Persistent feeder component for displaying feed items received from information feeds of online social networks

ABSTRACT

Disclosed are methods, apparatus, systems, and computer readable storage media for providing a persistent feeder component in a user interface to display in near real-time feed items when received in information feeds of online social networks. The feed items can come from feeds of multiple online social networks to be displayed in a single feeder component, and the feeder component may be configured to display proximate to each feed item a graphical indicator identifying the information feed of the feed item. The feeder component can be displayed in one of multiple display formats. The feeder component may also be configured to track activity on an online social network and display a notification when activity on the online social network has met one or more milestones determined by the user.

PRIORITY AND RELATED APPLICATION DATA

This patent document claims priority to commonly assigned U.S.Provisional Patent Application No. 61/751,138, titled “ComputerImplemented Methods and Apparatus for Providing a Persistent FeederComponent to Display Feed Items Received from Information Feeds ofOnline Social Networks”, by Rajagopal et al., filed on Jan. 10, 2013,which is hereby incorporated by reference in its entirety and for allpurposes.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material,which is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

This patent document relates generally to providing on-demand servicesin an online social network using a database system and, morespecifically, to techniques for assisting users of social network datain composing social media messages.

BACKGROUND

“Cloud computing” services provide shared resources, software, andinformation to computers and other devices upon request. In cloudcomputing environments, software can be accessible over the Internetrather than installed locally on in-house computer systems. Cloudcomputing typically involves over-the-Internet provision of dynamicallyscalable and often virtualized resources. Technological details can beabstracted from the users, who no longer have need for expertise in, orcontrol over, the technology infrastructure “in the cloud” that supportsthem.

Database resources can be provided in a cloud computing context.However, using conventional database management techniques, it isdifficult to know about the activity of other users of a database systemin the cloud or other network. For example, the actions of a particularuser, such as a salesperson, on a database resource may be important tothe user's boss. The user can create a report about what the user hasdone and send it to the boss, but such reports may be inefficient, nottimely, and incomplete. Also, it may be difficult to identify otherusers who might benefit from the information in the report.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and operations for the disclosedinventive systems, apparatus, and methods for providing a persistentfeeder component to display feed items received from information feedsof online social networks. These drawings in no way limit any changes inform and detail that may be made by one skilled in the art withoutdeparting from the spirit and scope of the disclosed implementations.

FIG. 1A shows a block diagram of an example of an environment 10 inwhich an on-demand database service can be used in accordance with someimplementations.

FIG. 1B shows a block diagram of an example of some implementations ofelements of FIG. 1A and various possible interconnections between theseelements.

FIG. 2A shows a system diagram illustrating an example of architecturalcomponents of an on-demand database service environment 200 according tosome implementations.

FIG. 2B shows a system diagram further illustrating an example ofarchitectural components of an on-demand database service environmentaccording to some implementations.

FIG. 2C shows a simplified system diagram showing two on-demand databaseservice environments 200A and 200B according to some implementations.

FIG. 3 shows a flowchart of an example of a method 300 for trackingupdates to a record stored in a database system, performed in accordancewith some implementations.

FIG. 4 shows a block diagram of an example of components of a databasesystem configuration 400 performing a method for tracking an update to arecord according to some implementations.

FIG. 5 shows a flowchart of an example of a method 500 for trackingactions of a user of a database system, performed in accordance withsome implementations.

FIG. 6 shows a flowchart of an example of a method 600 for creating anews feed from messages created by a user about a record or anotheruser, performed in accordance with some implementations.

FIG. 7 shows an example of a group feed on a group page according tosome implementations.

FIG. 8 shows an example of a record feed containing a feed trackedupdate, post, and comments according to some implementations.

FIG. 9A shows an example of a plurality of tables that may be used intracking events and creating feeds according to some implementations.

FIG. 9B shows a flowchart of an example of a method 900 forautomatically subscribing a user to an object in a database system,performed in accordance with some implementations.

FIG. 10 shows a flowchart of an example of a method 1000 for savinginformation to feed tracking tables, performed in accordance with someimplementations.

FIG. 11 shows a flowchart of an example of a method 1100 for reading afeed item as part of generating a feed for display, performed inaccordance with some implementations.

FIG. 12 shows a flowchart of an example of a method 1200 for reading afeed item of a profile feed for display, performed in accordance withsome implementations.

FIG. 13 shows a flowchart of an example of a method 1300 of storingevent information for efficient generation of feed items to display in afeed, performed in accordance with some implementations.

FIG. 14 shows a flowchart of an example of a method 1400 for creating acustom feed for users of a database system using filtering criteria,performed in accordance with some implementations.

FIG. 15 shows a flowchart of an example of a method 1500 for providing apersistent feeder component in a user interface to display in nearreal-time feed items when received in information feeds of online socialnetworks, performed in accordance with some implementations.

FIG. 16 shows a flowchart of an example of a method 1600 for providing apersistent feeder component in a user interface to display in nearreal-time feed items when received in information feeds of online socialnetworks, performed in accordance with some implementations.

FIG. 17 shows a flowchart of an example of a method 1700 for providing apersistent feeder component in a user interface to display in nearreal-time feed items when received in information feeds of online socialnetworks, performed in accordance with some implementations.

FIG. 18 shows a flowchart of an example of a method 1830 for receivingand responding to user input data, as one of various implementations ofblock 1730 of method 1700.

FIG. 19 shows a flowchart of an example of a method 1930 for receivingand responding to user input data, as another one of variousimplementations of block 1730 of method 1700.

FIG. 20 shows a flowchart of an example of a method 2030 for receivingand responding to user input data, as yet another one of variousimplementations of block 1730 of method 1700.

FIG. 21 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent superimposed over a portion of the page as displayed on adisplay device, according to some implementations.

FIG. 22 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent superimposed over a portion of the page as displayed on adisplay device, according to some implementations.

FIG. 23 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent as a separate pop-out window superimposed over a portion ofthe page as displayed on a display device, according to someimplementations.

FIG. 24 shows a zoomed-in view of an example of a graphical userinterface (GUI) including a presentation of a social networking pagewith a feed and a feeder component superimposed over a portion of thepage as displayed on a display device, according to someimplementations.

DETAILED DESCRIPTION

Examples of systems, apparatus, and methods according to the disclosedimplementations are described in this section. These examples are beingprovided solely to add context and aid in the understanding of thedisclosed implementations. It will thus be apparent to one skilled inthe art that implementations may be practiced without some or all ofthese specific details. In other instances, certain process/methodoperations, also referred to herein as “blocks,” have not been describedin detail in order to avoid unnecessarily obscuring implementations.Other applications are possible, such that the following examples shouldnot be taken as definitive or limiting either in scope or setting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific implementations. Althoughthese implementations are described in sufficient detail to enable oneskilled in the art to practice the disclosed implementations, it isunderstood that these examples are not limiting, such that otherimplementations may be used and changes may be made without departingfrom their spirit and scope. For example, the blocks of methods shownand described herein are not necessarily performed in the orderindicated. It should also be understood that the methods may includemore or fewer blocks than are indicated. In some implementations, blocksdescribed herein as separate blocks may be combined. Conversely, whatmay be described herein as a single block may be implemented in multipleblocks.

Various implementations described or referenced herein are directed todifferent methods, apparatus, systems, and computer-readable storagemedia for providing a persistent feeder component in a user interface todisplay in near real-time feed items when received in information feedsof online social networks, also referred to herein as social networkingsystems. One example of an online social network is Chatter®, providedby salesforce.com, inc. of San Francisco, Calif. Online social networksare increasingly becoming a common way to facilitate communication amongpeople and groups of people, any of whom can be recognized as users of asocial networking system. Some online social networks can be implementedin various settings, including organizations, e.g., enterprises such ascompanies or business partnerships, academic institutions, or groupswithin such an organization. For instance, Chatter® can be used byemployee users in a division of a business organization to share data,communicate, and collaborate with each other for various purposes.

In some online social networks, users can access one or more informationfeeds, which include information updates presented as feed items or feedentries. Such a feed item can include a single information update or acollection of individual information updates. A feed item can includevarious types of data including character-based data, audio data, imagedata and/or video data. An information feed can be displayed in agraphical user interface (GUI) on a display device such as the displayof a computing device as described below. The information updates caninclude various social network data from various sources and can bestored in an on-demand database service environment. In someimplementations, the disclosed methods, apparatus, systems, andcomputer-readable storage media may be configured or designed for use ina multi-tenant database environment.

In some implementations, an online social network may allow a user tofollow data objects in the form of records such as cases, accounts, oropportunities, in addition to following individual users and groups ofusers. The “following” of a record stored in a database, as described ingreater detail below, allows a user to track the progress of thatrecord. Updates to the record, also referred to herein as changes to therecord, are one type of information update that can occur and be notedon an information feed such as a record feed or a news feed of a usersubscribed to the record. Examples of record updates include fieldchanges in the record, updates to the status of a record, as well as thecreation of the record itself. Some records are publicly accessible,such that any user can follow the record, while other records areprivate, for which appropriate security clearance/permissions are aprerequisite to a user following the record.

Information updates can include various types of updates, which may ormay not be linked with a particular record. For example, informationupdates can be user-submitted messages or can otherwise be generated inresponse to user actions or in response to events. Examples of messagesinclude: posts, comments, indications of a user's personal preferencessuch as “likes” and “dislikes”, updates to a user's status, uploadedfiles, and hyperlinks to social network data or other network data suchas various documents and/or web pages on the Internet. Posts can includealpha-numeric or other character-based user inputs such as words,phrases, statements, questions, emotional expressions, and/or symbols.Comments generally refer to responses to posts, such as words, phrases,statements, answers, questions, and reactionary emotional expressionsand/or symbols. Multimedia data can be included in, linked with, orattached to a post or comment. For example, a post can include textualstatements in combination with a JPEG image or animated image. A like ordislike can be submitted in response to a particular post or comment.Examples of uploaded files include presentations, documents, multimediafiles, and the like.

Users can follow a record by subscribing to the record, as mentionedabove. Users can also follow other entities such as other types of dataobjects, other users, and groups of users. Feed tracked updatesregarding such entities are one type of information update that can bereceived and included in the user's news feed. Any number of users canfollow a particular entity and thus view information updates pertainingto that entity on the users' respective news feeds. In some socialnetworks, users may follow each other by establishing connections witheach other, sometimes referred to as “friending” one another. Byestablishing such a connection, one user may be able to see informationgenerated by, generated about, or otherwise associated with anotheruser. For instance, a first user may be able to see information postedby a second user to the second user's personal social network page. Oneimplementation of such a personal social network page is a user'sprofile page, for example, in the form of a web page representing theuser's profile. In one example, when the first user is following thesecond user, the first user's news feed can receive a post from thesecond user submitted to the second user's profile feed, also referredto herein as the user's “wall,” which is one example of an informationfeed displayed on the user's profile page.

In some implementations, an information feed may be specific to a groupof users of an online social network. For instance, a group of users maypublish a news feed. Members of the group may view and post to thisgroup feed in accordance with a permissions configuration for the feedand the group. Information updates in a group context can also includechanges to group status information.

In some implementations, when data such as posts or comments input fromone or more users are submitted to an information feed for a particularuser, group, object, or other construct within an online social network,an email notification or other type of network communication may betransmitted to all users following the user, group, or object inaddition to the inclusion of the data as a feed item in one or morefeeds, such as a user's profile feed, a news feed, or a record feed. Insome online social networks, the occurrence of such a notification islimited to the first instance of a published input, which may form partof a larger conversation. For instance, a notification may betransmitted for an initial post, but not for comments on the post. Insome other implementations, a separate notification is transmitted foreach such information update.

Some implementations of the disclosed systems, apparatus, methods, andcomputer readable storage media are configured to display a feedercomponent in a user interface displayed on a display device, such as thedisplay of a user's smartphone. The feeder component can be configuredto display feed items from one or more information feeds. For instance,the feeder component can receive feed items from various differentonline social networks, such as Chatter®, Facebook®, and/or Twitter®,and combine the feed items into a single or presentation in the form ofthe feeder component. In addition, some implementations of the disclosedfeeder components are configured to be maintained in the user interface,for example, in a window generated by a web browser program, regardlessof which web pages are loaded and displayed. Thus, the feeder componentcan persist when the user interface changes among states, i.e., whendifferent presentations of pages or other data are displayed in the userinterface.

For instance, a user of his enterprise's implementation of Chatter® maybe following co-workers, groups, records, and other entities related tothe user's job and thus need to keep a close eye on his Chatter® feedthroughout the work day. However, the user may wish to simultaneouslymonitor his Facebook® feed, for instance, to confirm or modify a socialengagement immediately following the work day. Rather than having tonavigate to the feed tab in Chatter® every time the user wishes to viewChatter® information updates, and/or have to open up a separate browserwindow to view Facebook® information updates, the user can activate andmonitor a persistent feeder component regardless of which pages the usernavigates to during a browsing session, such as pages of hisenterprise's implementation of Chatter®. In this way, the user canalways view feed items in the feeder component irrespective of whichpage is currently displayed. For example, the feeder component canremain open and superimposed over the contents of Chatter® pages loadedin the user interface displayed on the user's computing device. Someimplementations of the disclosed techniques thus provide a user withimmediate access to his Chatter®, Facebook®, and other social networkfeeds without requiring action on the part of the user, such asnavigation away from an active web page.

Moreover, because one or more information feeds may contain moreinformation than the user is interested in viewing in his feedercomponent, the user may set one or more parameters to filter the feeditems to determine which feed items or portions of content of feed itemsto present in the feeder component. In some instances, parameters can beselected, user-generated, and customized according to a user's personalpreferences. In some instances, one or more parameters can be defaultparameters defined for a specific online social network. In someinstances, one or more parameters can be defined by a systemadministrator of the online social network. Thus, using someimplementations of the disclosed techniques, rather than having tomanually navigate and read through any number of posts and commentsrecently published in a feed or a combination of feeds, the user canselect and customize parameters to specify the types of posts andcomments that he would like to view in the feeder component. Forexample, if a Chatter® user is interested in viewing posts in his feedercomponent that have to do with a particular case that he is interestedin, he can enter the case number or the case title as a user-definedkeyword parameter. As information updates are received by a computingdevice such as a server or the user's smartphone, the computing deviceapplies the parameters to the information updates, and only the filteredresults are displayed in the feeder component. That is, informationupdates that do not satisfy the parameters are excluded from the feedercomponent. The user can then be presented with a subset of feed items ofgreater relevance and interest to him based on the parameters.

In the same example, the user may also have access to a Twitter® feedand may be interested in receiving in his Chatter® feeder componenttweets that have to do with the client involved in the case that he isfollowing in his Chatter® feed. Rather than having to track Twitter®updates in a separate browser window or tab, the user can configure hisChatter® feeder component to show, in addition to the Chatter®information updates, Twitter® tweets that he is interested in. Moreover,the user can set user-defined parameters to specify what kinds of tweetshe would like to be displayed in the feeder component.

In some implementations, login credentials for respective online socialnetworks can be transmitted directly to the appropriate online socialnetwork for authentication, using a protocol such as OAuth. Once theuser is authenticated, for instance, on Facebook®, a Facebook® servermay return an access token that a Chatter® server may use to retrievepertinent feed items from Facebook®. This way, the user's logincredentials for Facebook® need not be stored in Chatter®, thus providingmore robust security.

In some implementations, the display format of the feeder component canbe changed by the user's input. In one example, the feeder componentappears as an in-page textbox superimposed over a portion of thedisplayed page. In another example, the feeder component may appear as aminimized indicator superimposed over a portion such as a taskbar of thedisplayed page. For example, the minimized indicator may be a bar oftext along the bottom of the displayed page in a button that the usermay click on to show the feeder component in the in-page textbox format.In another example, the feeder component may appear as a pop-out browserwindow, separate from the browser window in which the page is displayed.The pop-out browser window display format may allow the user to view alarger resizable version of the feeder component, allowing the user tomore conveniently view more feed items at one time.

In some implementations, the feeder component may be in an enabled stateor a disabled state. In one example, the feeder component may be in adisabled state when the feeder component is first activated. Thedisabled state can serve to reduce unnecessary network traffic caused byregular requests for information updates. The feeder component may beenabled or disabled by the user by changing his preference settingsstored as part of the user's profile on Chatter®. In some examples, whenin the enabled state, the user may choose to disable the feedercomponent by clicking on an appropriate icon in the feeder component.While the feeder component is in a disabled state, the feeder componentmay be hidden from view, and requests for feed items will neither betransmitted nor received.

These and other implementations may be embodied in various types ofhardware, software, firmware, and combinations thereof. For example,some techniques disclosed herein may be implemented, at least in part,by computer-readable media that include program instructions, stateinformation, etc., for performing various services and operationsdescribed herein. Examples of program instructions include both machinecode, such as produced by a compiler, and files containing higher-levelcode that may be executed by a computing device such as a server orother data processing apparatus using an interpreter. Examples ofcomputer-readable media include, but are not limited to, magnetic mediasuch as hard disks, floppy disks, and magnetic tape; optical media suchas CD-ROM disks; magneto-optical media; and hardware devices that arespecially configured to store program instructions, such as read-onlymemory (“ROM”) devices and random access memory (“RAM”) devices. Theseand other features of the disclosed implementations will be described inmore detail below with reference to the associated drawings.

The term “multi-tenant database system” can refer to those systems inwhich various elements of hardware and software of a database system maybe shared by one or more customers. For example, a given applicationserver may simultaneously process requests for a great number ofcustomers, and a given database table may store rows of data such asfeed items for a potentially much greater number of customers. The term“query plan” generally refers to one or more operations used to accessinformation in a database system.

A “user profile” or “user's profile” is generally configured to storeand maintain data about a given user of the database system. The datacan include general information, such as name, title, phone number, aphoto, a biographical summary, and a status, e.g., text describing whatthe user is currently doing. As mentioned below, the data can includemessages created by other users. Where there are multiple tenants, auser is typically associated with a particular tenant. For example, auser could be a salesperson of a company, which is a tenant of thedatabase system that provides a database service.

The term “record” generally refers to a data entity, such as an instanceof a data object created by a user of the database service, for example,about a particular (actual or potential) business relationship orproject. The data object can have a data structure defined by thedatabase service (a standard object) or defined by a user (customobject). For example, a record can be for a business partner orpotential business partner (e.g., a client, vendor, distributor, etc.)of the user, and can include information describing an entire company,subsidiaries, or contacts at the company. As another example, a recordcan be a project that the user is working on, such as an opportunity(e.g., a possible sale) with an existing partner, or a project that theuser is trying to get. In one implementation of a multi-tenant databasesystem, each record for the tenants has a unique identifier stored in acommon table. A record has data fields that are defined by the structureof the object (e.g., fields of certain data types and purposes). Arecord can also have custom fields defined by a user. A field can beanother record or include links thereto, thereby providing aparent-child relationship between the records.

The terms “information feed” and “feed” are used interchangeably hereinand generally refer to a combination (e.g., a list) of feed items orentries with various types of information and data. Such feed items canbe stored and maintained in one or more database tables, e.g., as rowsin the table(s), that can be accessed to retrieve relevant informationto be presented as part of a displayed feed. The term “feed item” (orfeed element) refers to an item of information, which can be presentedin the feed such as a post submitted by a user. Feed items ofinformation about a user can be presented in a user's profile feed ofthe database, while feed items of information about a record can bepresented in a record feed in the database, by way of example. A profilefeed and a record feed are examples of different information feeds. Asecond user following a first user and a record can receive the feeditems associated with the first user and the record for display in thesecond user's news feed, which is another type of information feed. Insome implementations, the feed items from any number of followed usersand records can be combined into a single information feed of aparticular user.

As examples, a feed item can be a message, such as a user-generated postof text data, and a feed tracked update to a record or profile, such asa change to a field of the record. Feed tracked updates are described ingreater detail below. A feed can be a combination of messages and feedtracked updates. Messages include text created by a user, and mayinclude other data as well. Examples of messages include posts, userstatus updates, and comments. Messages can be created for a user'sprofile or for a record. Posts can be created by various users,potentially any user, although some restrictions can be applied. As anexample, posts can be made to a wall section of a user's profile page(which can include a number of recent posts) or a section of a recordthat includes multiple posts. The posts can be organized inchronological order when displayed in a graphical user interface (GUI),for instance, on the user's profile page, as part of the user's profilefeed. In contrast to a post, a user status update changes a status of auser and can be made by that user or an administrator. A record can alsohave a status, the update of which can be provided by an owner of therecord or other users having suitable write access permissions to therecord. The owner can be a single user, multiple users, or a group. Inone implementation, there is only one status for a record.

In some implementations, a comment can be made on any feed item. In someimplementations, comments are organized as a list explicitly tied to aparticular feed tracked update, post, or status update. In someimplementations, comments may not be listed in the first layer (in ahierarchal sense) of feed items, but listed as a second layer branchingfrom a particular first layer feed item.

A “feed tracked update,” also referred to herein as a “informationupdate,” is one type of information update and generally refers to datarepresenting an event. A feed tracked update can include text generatedby the database system in response to the event, to be provided as oneor more feed items for possible inclusion in one or more feeds. In oneimplementation, the data can initially be stored, and then the databasesystem can later use the data to create text for describing the event.Both the data and/or the text can be a feed tracked update, as usedherein. In various implementations, an event can be an update of arecord and/or can be triggered by a specific action by a user. Whichactions trigger an event can be configurable. Which events have feedtracked updates created and which information updates are sent to whichusers can also be configurable. Messages and information updates can bestored as a field or child object of the record. For example, the feedcan be stored as a child object of the record.

A “group” is generally a collection of users. In some implementations,the group may be defined as users with a same or similar attribute, orby membership. In some implementations, a “group feed”, also referred toherein as a “group news feed”, includes one or more feed items about anyuser in the group. In some implementations, the group feed also includesinformation updates and other feed items that are about the group as awhole, the group's purpose, the group's description, and group recordsand other objects stored in association with the group. Threads ofinformation updates including group record updates and messages, such asposts, comments, likes, etc., can define group conversations and changeover time.

An “entity feed” or “record feed” generally refers to a feed of feeditems about a particular record in the database, such as feed trackedupdates about changes to the record and posts made by users about therecord. An entity feed can be composed of any type of feed item. Such afeed can be displayed on a page such as a web page associated with therecord, e.g., a home page of the record. As used herein, a “profilefeed” or “user's profile feed” is a feed of feed items about aparticular user. In one example, the feed items for a profile feedinclude posts and comments that other users make about or send to theparticular user, and status updates made by the particular user. Such aprofile feed can be displayed on a page associated with the particularuser. In another example, feed items in a profile feed could includeposts made by the particular user and feed tracked updates initiatedbased on actions of the particular user.

I. General Overview

Systems, apparatus, and methods are provided for implementing enterpriselevel social and business information networking. Such implementationscan provide more efficient use of a database system. For instance, auser of a database system may not easily know when important informationin the database has changed, e.g., about a project or client.Implementations can provide feed tracked updates about such changes andother events, thereby keeping users informed.

By way of example, a user can update a record, e.g., an opportunity suchas a possible sale of 1000 computers. Once the record update has beenmade, a feed tracked update about the record update can thenautomatically be provided, e.g., in a feed, to anyone subscribing to theopportunity or to the user. Thus, the user does not need to contact amanager regarding the change in the opportunity, since the feed trackedupdate about the update is sent via a feed right to the manager's feedpage or other page.

Next, mechanisms and methods for providing systems implementingenterprise level social and business information networking will bedescribed with reference to several implementations. First, an overviewof an example of a database system is described, and then examples oftracking events for a record, actions of a user, and messages about auser or record are described. Various implementations about the datastructure of feeds, customizing feeds, user selection of records andusers to follow, generating feeds, and displaying feeds are alsodescribed.

II. System Overview

FIG. 1A shows a block diagram of an example of an environment 10 inwhich an on-demand database service can be used in accordance with someimplementations. Environment 10 may include user systems 12, network 14,database system 16, processor system 17, application platform 18,network interface 20, tenant data storage 22, system data storage 24,program code 26, and process space 28. In other implementations,environment 10 may not have all of these components and/or may haveother components instead of, or in addition to, those listed above.

Environment 10 is an environment in which an on-demand database serviceexists. User system 12 may be implemented as any computing device(s) orother data processing apparatus such as a machine or system that is usedby a user to access a database system 16. For example, any of usersystems 12 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of such computing devices. Asillustrated in FIG. 1A (and in more detail in FIG. 1B) user systems 12might interact via a network 14 with an on-demand database service,which is implemented in the example of FIG. 1A as database system 16.

An on-demand database service, implemented using system 16 by way ofexample, is a service that is made available to outside users, who donot need to necessarily be concerned with building and/or maintainingthe database system. Instead, the database system may be available fortheir use when the users need the database system, i.e., on the demandof the users. Some on-demand database services may store informationfrom one or more tenants into tables of a common database image to forma multi-tenant database system (MTS). A database image may include oneor more database objects. A relational database management system(RDBMS) or the equivalent may execute storage and retrieval ofinformation against the database object(s). Application platform 18 maybe a framework that allows the applications of system 16 to run, such asthe hardware and/or software, e.g., the operating system. In someimplementations, application platform 18 enables creation, managing andexecuting one or more applications developed by the provider of theon-demand database service, users accessing the on-demand databaseservice via user systems 12, or third party application developersaccessing the on-demand database service via user systems 12.

The users of user systems 12 may differ in their respective capacities,and the capacity of a particular user system 12 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 12 tointeract with system 16, that user system has the capacities allotted tothat salesperson. However, while an administrator is using that usersystem to interact with system 16, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level, also called authorization.

Network 14 is any network or combination of networks of devices thatcommunicate with one another. For example, network 14 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. Network 14 can include a TCP/IP (Transfer ControlProtocol and Internet Protocol) network, such as the global internetworkof networks often referred to as the “Internet” with a capital “I.” TheInternet will be used in many of the examples herein. However, it shouldbe understood that the networks that the present implementations mightuse are not so limited, although TCP/IP is a frequently implementedprotocol.

User systems 12 might communicate with system 16 using TCP/IP and, at ahigher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 12 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP signals to and from anHTTP server at system 16. Such an HTTP server might be implemented asthe sole network interface 20 between system 16 and network 14, butother techniques might be used as well or instead. In someimplementations, the network interface 20 between system 16 and network14 includes load sharing functionality, such as round-robin HTTP requestdistributors to balance loads and distribute incoming HTTP requestsevenly over a plurality of servers. At least for users accessing system16, each of the plurality of servers has access to the MTS' data;however, other alternative configurations may be used instead.

In one implementation, system 16, shown in FIG. 1A, implements aweb-based customer relationship management (CRM) system. For example, inone implementation, system 16 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, web pages and other information to and fromuser systems 12 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject in tenant data storage 22, however, tenant data typically isarranged in the storage medium(s) of tenant data storage 22 so that dataof one tenant is kept logically separate from that of other tenants sothat one tenant does not have access to another tenant's data, unlesssuch data is expressly shared. In certain implementations, system 16implements applications other than, or in addition to, a CRMapplication. For example, system 16 may provide tenant access tomultiple hosted (standard and custom) applications, including a CRMapplication. User (or third party developer) applications, which may ormay not include CRM, may be supported by the application platform 18,which manages creation, storage of the applications into one or moredatabase objects and executing of the applications in a virtual machinein the process space of the system 16.

One arrangement for elements of system 16 is shown in FIGS. 1A and 1B,including a network interface 20, application platform 18, tenant datastorage 22 for tenant data 23, system data storage 24 for system data 25accessible to system 16 and possibly multiple tenants, program code 26for implementing various functions of system 16, and a process space 28for executing MTS system processes and tenant-specific processes, suchas running applications as part of an application hosting service.Additional processes that may execute on system 16 include databaseindexing processes.

Several elements in the system shown in FIG. 1A include conventional,well-known elements that are explained only briefly here. For example,each user system 12 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. The term “computing device” is also referred to hereinsimply as a “computer”. User system 12 typically runs an HTTP client,e.g., a browsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 12 to access, process and view information, pages andapplications available to it from system 16 over network 14. Each usersystem 12 also typically includes one or more user input devices, suchas a keyboard, a mouse, trackball, touch pad, touch screen, pen or thelike, for interacting with a graphical user interface (GUI) provided bythe browser on a display (e.g., a monitor screen, LCD display, etc.) ofthe computing device in conjunction with pages, forms, applications andother information provided by system 16 or other systems or servers. Forexample, the user interface device can be used to access data andapplications hosted by system 16, and to perform searches on storeddata, and otherwise allow a user to interact with various GUI pages thatmay be presented to a user. As discussed above, implementations aresuitable for use with the Internet, although other networks can be usedinstead of or in addition to the Internet, such as an intranet, anextranet, a virtual private network (VPN), a non-TCP/IP based network,any LAN or WAN or the like.

According to one implementation, each user system 12 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 16(and additional instances of an MTS, where more than one is present) andall of its components might be operator configurable usingapplication(s) including computer code to run using processor system 17,which may be implemented to include a central processing unit, which mayinclude an Intel Pentium® processor or the like, and/or multipleprocessor units. Non-transitory computer-readable media can haveinstructions stored thereon/in, that can be executed by or used toprogram a computing device to perform any of the methods of theimplementations described herein. Computer program code 26 implementinginstructions for operating and configuring system 16 to intercommunicateand to process web pages, applications and other data and media contentas described herein is preferably downloadable and stored on a harddisk, but the entire program code, or portions thereof, may also bestored in any other volatile or non-volatile memory medium or device asis well known, such as a ROM or RAM, or provided on any media capable ofstoring program code, such as any type of rotating media includingfloppy disks, optical discs, digital versatile disk (DVD), compact disk(CD), microdrive, and magneto-optical disks, and magnetic or opticalcards, nanosystems (including molecular memory ICs), or any other typeof computer-readable medium or device suitable for storing instructionsand/or data. Additionally, the entire program code, or portions thereof,may be transmitted and downloaded from a software source over atransmission medium, e.g., over the Internet, or from another server, asis well known, or transmitted over any other conventional networkconnection as is well known (e.g., extranet, VPN, LAN, etc.) using anycommunication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet,etc.) as are well known. It will also be appreciated that computer codefor the disclosed implementations can be realized in any programminglanguage that can be executed on a client system and/or server or serversystem such as, for example, C, C++, HTML, any other markup language,Java™, JavaScript, ActiveX, any other scripting language, such asVBScript, and many other programming languages as are well known may beused. (Java™ is a trademark of Sun Microsystems, Inc.).

According to some implementations, each system 16 is configured toprovide web pages, forms, applications, data and media content to user(client) systems 12 to support the access by user systems 12 as tenantsof system 16. As such, system 16 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant to referto a computing device or system, including processing hardware andprocess space(s), an associated storage medium such as a memory deviceor database, and, in some instances, a database application (e.g.,OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database objects described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 1B shows a block diagram of an example of some implementations ofelements of FIG. 1A and various possible interconnections between theseelements. That is, FIG. 1B also illustrates environment 10. However, inFIG. 1B elements of system 16 and various interconnections in someimplementations are further illustrated. FIG. 1B shows that user system12 may include processor system 12A, memory system 12B, input system12C, and output system 12D. FIG. 1B shows network 14 and system 16. FIG.1B also shows that system 16 may include tenant data storage 22, tenantdata 23, system data storage 24, system data 25, User Interface (UI) 30,Application Program Interface (API) 32, PL/SOQL 34, save routines 36,application setup mechanism 38, applications servers 1001-100N, systemprocess space 102, tenant process spaces 104, tenant management processspace 110, tenant storage space 112, user storage 114, and applicationmetadata 116. In other implementations, environment 10 may not have thesame elements as those listed above and/or may have other elementsinstead of, or in addition to, those listed above.

User system 12, network 14, system 16, tenant data storage 22, andsystem data storage 24 were discussed above in FIG. 1A. Regarding usersystem 12, processor system 12A may be any combination of one or moreprocessors. Memory system 12B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 12Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 12D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 1B, system 16 may include a network interface 20 (of FIG. 1A)implemented as a set of HTTP application servers 100, an applicationplatform 18, tenant data storage 22, and system data storage 24. Alsoshown is system process space 102, including individual tenant processspaces 104 and a tenant management process space 110. Each applicationserver 100 may be configured to communicate with tenant data storage 22and the tenant data 23 therein, and system data storage 24 and thesystem data 25 therein to serve requests of user systems 12. The tenantdata 23 might be divided into individual tenant storage spaces 112,which can be either a physical arrangement and/or a logical arrangementof data. Within each tenant storage space 112, user storage 114 andapplication metadata 116 might be similarly allocated for each user. Forexample, a copy of a user's most recently used (MRU) items might bestored to user storage 114. Similarly, a copy of MRU items for an entireorganization that is a tenant might be stored to tenant storage space112. A UI 30 provides a user interface and an API 32 provides anapplication programmer interface to system 16 resident processes tousers and/or developers at user systems 12. The tenant data and thesystem data may be stored in various databases, such as one or moreOracle databases.

Application platform 18 includes an application setup mechanism 38 thatsupports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage 22by save routines 36 for execution by subscribers as one or more tenantprocess spaces 104 managed by tenant management process 110 for example.Invocations to such applications may be coded using PL/SOQL 34 thatprovides a programming language style interface extension to API 32. Adetailed description of some PL/SOQL language implementations isdiscussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHODAND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA AMULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, issued onJun. 1, 2010, and hereby incorporated by reference in its entirety andfor all purposes. Invocations to applications may be detected by one ormore system processes, which manage retrieving application metadata 116for the subscriber making the invocation and executing the metadata asan application in a virtual machine.

Each application server 100 may be communicably coupled to databasesystems, e.g., having access to system data 25 and tenant data 23, via adifferent network connection. For example, one application server 1001might be coupled via the network 14 (e.g., the Internet), anotherapplication server 100N−1 might be coupled via a direct network link,and another application server 100N might be coupled by yet a differentnetwork connection. Transfer Control Protocol and Internet Protocol(TCP/IP) are typical protocols for communicating between applicationservers 100 and the database system. However, it will be apparent to oneskilled in the art that other transport protocols may be used tooptimize the system depending on the network interconnect used.

In certain implementations, each application server 100 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 100. In one implementation, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 100 and the user systems 12 to distribute requests to theapplication servers 100. In one implementation, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 100. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain implementations, three consecutive requests from the same usercould hit three different application servers 100, and three requestsfrom different users could hit the same application server 100. In thismanner, by way of example, system 16 is multi-tenant, wherein system 16handles storage of, and access to, different objects, data andapplications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 16 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 22). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 16 that are allocated atthe tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant-specific data, system 16 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain implementations, user systems 12 (which may be clientsystems) communicate with application servers 100 to request and updatesystem-level and tenant-level data from system 16 that may involvesending one or more queries to tenant data storage 22 and/or system datastorage 24. System 16 (e.g., an application server 100 in system 16)automatically generates one or more SQL statements (e.g., one or moreSQL queries) that are designed to access the desired information. Systemdata storage 24 may generate query plans to access the requested datafrom the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to some implementations. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forcase, account, contact, lead, and opportunity data objects, eachcontaining pre-defined fields. It should be understood that the word“entity” may also be used interchangeably herein with “object” and“table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. Commonly assigned U.S. Pat. No.7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASESYSTEM, by Weissman et al., issued on Aug. 17, 2010, and herebyincorporated by reference in its entirety and for all purposes, teachessystems and methods for creating custom objects as well as customizingstandard objects in a multi-tenant database system. In certainimplementations, for example, all custom entity data rows are stored ina single multi-tenant physical table, which may contain multiple logicaltables per organization. It is transparent to customers that theirmultiple “tables” are in fact stored in one large table or that theirdata may be stored in the same table as the data of other customers.

FIG. 2A shows a system diagram illustrating an example of architecturalcomponents of an on-demand database service environment 200 according tosome implementations. A client machine located in the cloud 204,generally referring to one or more networks in combination, as describedherein, may communicate with the on-demand database service environmentvia one or more edge routers 208 and 212. A client machine can be any ofthe examples of user systems 12 described above. The edge routers maycommunicate with one or more core switches 220 and 224 via firewall 216.The core switches may communicate with a load balancer 228, which maydistribute server load over different pods, such as the pods 240 and244. The pods 240 and 244, which may each include one or more serversand/or other computing resources, may perform data processing and otheroperations used to provide on-demand services. Communication with thepods may be conducted via pod switches 232 and 236. Components of theon-demand database service environment may communicate with a databasestorage 256 via a database firewall 248 and a database switch 252.

As shown in FIGS. 2A and 2B, accessing an on-demand database serviceenvironment may involve communications transmitted among a variety ofdifferent hardware and/or software components. Further, the on-demanddatabase service environment 200 is a simplified representation of anactual on-demand database service environment. For example, while onlyone or two devices of each type are shown in FIGS. 2A and 2B, someimplementations of an on-demand database service environment may includeanywhere from one to many devices of each type. Also, the on-demanddatabase service environment need not include each device shown in FIGS.2A and 2B, or may include additional devices not shown in FIGS. 2A and2B.

Moreover, one or more of the devices in the on-demand database serviceenvironment 200 may be implemented on the same physical device or ondifferent hardware. Some devices may be implemented using hardware or acombination of hardware and software. Thus, terms such as “dataprocessing apparatus,” “machine,” “server” and “device” as used hereinare not limited to a single hardware device, but rather include anyhardware and software configured to provide the described functionality.

The cloud 204 is intended to refer to a data network or plurality ofdata networks, often including the Internet. Client machines located inthe cloud 204 may communicate with the on-demand database serviceenvironment to access services provided by the on-demand databaseservice environment. For example, client machines may access theon-demand database service environment to retrieve, store, edit, and/orprocess information.

In some implementations, the edge routers 208 and 212 route packetsbetween the cloud 204 and other components of the on-demand databaseservice environment 200. The edge routers 208 and 212 may employ theBorder Gateway Protocol (BGP). The BGP is the core routing protocol ofthe Internet. The edge routers 208 and 212 may maintain a table of IPnetworks or ‘prefixes’, which designate network reachability amongautonomous systems on the Internet.

In one or more implementations, the firewall 216 may protect the innercomponents of the on-demand database service environment 200 fromInternet traffic. The firewall 216 may block, permit, or deny access tothe inner components of the on-demand database service environment 200based upon a set of rules and other criteria. The firewall 216 may actas one or more of a packet filter, an application gateway, a statefulfilter, a proxy server, or any other type of firewall.

In some implementations, the core switches 220 and 224 are high-capacityswitches that transfer packets within the on-demand database serviceenvironment 200. The core switches 220 and 224 may be configured asnetwork bridges that quickly route data between different componentswithin the on-demand database service environment. In someimplementations, the use of two or more core switches 220 and 224 mayprovide redundancy and/or reduced latency.

In some implementations, the pods 240 and 244 may perform the core dataprocessing and service functions provided by the on-demand databaseservice environment. Each pod may include various types of hardwareand/or software computing resources. An example of the pod architectureis discussed in greater detail with reference to FIG. 2B.

In some implementations, communication between the pods 240 and 244 maybe conducted via the pod switches 232 and 236. The pod switches 232 and236 may facilitate communication between the pods 240 and 244 and clientmachines located in the cloud 204, for example via core switches 220 and224. Also, the pod switches 232 and 236 may facilitate communicationbetween the pods 240 and 244 and the database storage 256.

In some implementations, the load balancer 228 may distribute workloadbetween the pods 240 and 244. Balancing the on-demand service requestsbetween the pods may assist in improving the use of resources,increasing throughput, reducing response times, and/or reducingoverhead. The load balancer 228 may include multilayer switches toanalyze and forward traffic.

In some implementations, access to the database storage 256 may beguarded by a database firewall 248. The database firewall 248 may act asa computer application firewall operating at the database applicationlayer of a protocol stack. The database firewall 248 may protect thedatabase storage 256 from application attacks such as structure querylanguage (SQL) injection, database rootkits, and unauthorizedinformation disclosure.

In some implementations, the database firewall 248 may include a hostusing one or more forms of reverse proxy services to proxy trafficbefore passing it to a gateway router. The database firewall 248 mayinspect the contents of database traffic and block certain content ordatabase requests. The database firewall 248 may work on the SQLapplication level atop the TCP/IP stack, managing applications'connection to the database or SQL management interfaces as well asintercepting and enforcing packets traveling to or from a databasenetwork or application interface.

In some implementations, communication with the database storage 256 maybe conducted via the database switch 252. The multi-tenant databasestorage 256 may include more than one hardware and/or softwarecomponents for handling database queries. Accordingly, the databaseswitch 252 may direct database queries transmitted by other componentsof the on-demand database service environment (e.g., the pods 240 and244) to the correct components within the database storage 256.

In some implementations, the database storage 256 is an on-demanddatabase system shared by many different organizations. The on-demanddatabase system may employ a multi-tenant approach, a virtualizedapproach, or any other type of database approach. An on-demand databasesystem is discussed in greater detail with reference to FIGS. 1A and 1B.

FIG. 2B shows a system diagram further illustrating an example ofarchitectural components of an on-demand database service environmentaccording to some implementations. The pod 244 may be used to renderservices to a user of the on-demand database service environment 200. Insome implementations, each pod may include a variety of servers and/orother systems. The pod 244 includes one or more content batch servers264, content search servers 268, query servers 282, file force servers286, access control system (ACS) servers 280, batch servers 284, and appservers 288. Also, the pod 244 includes database instances 290, quickfile systems (QFS) 292, and indexers 294. In one or moreimplementations, some or all communication between the servers in thepod 244 may be transmitted via the switch 236.

In some implementations, the app servers 288 may include a hardwareand/or software framework dedicated to the execution of procedures(e.g., programs, routines, scripts) for supporting the construction ofapplications provided by the on-demand database service environment 200via the pod 244. In some implementations, the hardware and/or softwareframework of an app server 288 is configured to execute operations ofthe services described herein, including performance of the blocks ofmethods described with reference to FIGS. 15-24. In alternativeimplementations, two or more app servers 288 may be included andcooperate to perform such methods, or one or more other serversdescribed herein can be configured to perform the disclosed methods.

The content batch servers 264 may handle requests internal to the pod.These requests may be long-running and/or not tied to a particularcustomer. For example, the content batch servers 264 may handle requestsrelated to log mining, cleanup work, and maintenance tasks.

The content search servers 268 may provide query and indexer functions.For example, the functions provided by the content search servers 268may allow users to search through content stored in the on-demanddatabase service environment.

The file force servers 286 may manage requests for information stored inthe Fileforce storage 298. The Fileforce storage 298 may storeinformation such as documents, images, and basic large objects (BLOBs).By managing requests for information using the file force servers 286,the image footprint on the database may be reduced.

The query servers 282 may be used to retrieve information from one ormore file systems. For example, the query system 282 may receiverequests for information from the app servers 288 and then transmitinformation queries to the NFS 296 located outside the pod.

The pod 244 may share a database instance 290 configured as amulti-tenant environment in which different organizations share accessto the same database. Additionally, services rendered by the pod 244 maycall upon various hardware and/or software resources. In someimplementations, the ACS servers 280 may control access to data,hardware resources, or software resources.

In some implementations, the batch servers 284 may process batch jobs,which are used to run tasks at specified times. Thus, the batch servers284 may transmit instructions to other servers, such as the app servers288, to trigger the batch jobs.

In some implementations, the QFS 292 may be an open source file systemavailable from Sun Microsystems® of Santa Clara, Calif. The QFS mayserve as a rapid-access file system for storing and accessinginformation available within the pod 244. The QFS 292 may support somevolume management capabilities, allowing many disks to be groupedtogether into a file system. File system metadata can be kept on aseparate set of disks, which may be useful for streaming applicationswhere long disk seeks cannot be tolerated. Thus, the QFS system maycommunicate with one or more content search servers 268 and/or indexers294 to identify, retrieve, move, and/or update data stored in thenetwork file systems 296 and/or other storage systems.

In some implementations, one or more query servers 282 may communicatewith the NFS 296 to retrieve and/or update information stored outside ofthe pod 244. The NFS 296 may allow servers located in the pod 244 toaccess information to access files over a network in a manner similar tohow local storage is accessed.

In some implementations, queries from the query servers 222 may betransmitted to the NFS 296 via the load balancer 228, which maydistribute resource requests over various resources available in theon-demand database service environment. The NFS 296 may also communicatewith the QFS 292 to update the information stored on the NFS 296 and/orto provide information to the QFS 292 for use by servers located withinthe pod 244.

In some implementations, the pod may include one or more databaseinstances 290. The database instance 290 may transmit information to theQFS 292. When information is transmitted to the QFS, it may be availablefor use by servers within the pod 244 without using an additionaldatabase call.

In some implementations, database information may be transmitted to theindexer 294. Indexer 294 may provide an index of information availablein the database 290 and/or QFS 292. The index information may beprovided to file force servers 286 and/or the QFS 292.

III. Tracking Updates to a Record Stored in a Database

As multiple users might be able to change the data of a record, it canbe useful for certain users to be notified when a record is updated.Also, even if a user does not have authority to change a record, theuser still might want to know when there is an update to the record. Forexample, a vendor may negotiate a new price with a salesperson ofcompany X, where the salesperson is a user associated with tenant Y. Aspart of creating a new invoice or for accounting purposes, thesalesperson can change the price saved in the database. It may beimportant for co-workers to know that the price has changed. Thesalesperson could send an email to certain people, but this is onerousand the salesperson might not email all of the people who need to knowor want to know. Accordingly, some implementations of the disclosedtechniques can inform others (e.g., co-workers) who want to know aboutan update to a record automatically.

FIG. 3 shows a flowchart of an example of a method 300 for trackingupdates to a record stored in a database system, performed in accordancewith some implementations. Method 300 (and other methods describedherein) may be implemented at least partially with multi-tenant databasesystem 16, e.g., by one or more processors configured to receive orretrieve information, process the information, store results, andtransmit the results. In other implementations, method 300 may beimplemented at least partially with a single tenant database system. Invarious implementations, blocks may be omitted, combined, or split intoadditional blocks for method 300, as well as for other methods describedherein.

In block 310, the database system receives a request to update a firstrecord. In one implementation, the request is received from a firstuser. For example, a user may be accessing a page associated with thefirst record, and may change a displayed field and hit save. In anotherimplementation, the database system can automatically create therequest. For instance, the database system can create the request inresponse to another event, e.g., a request to change a field could besent periodically at a particular date and/or time of day, or a changeto another field or object. The database system can obtain a new valuebased on other fields of a record and/or based on parameters in thesystem.

The request for the update of a field of a record is an example of anevent associated with the first record for which a feed tracked updatemay be created. In other implementations, the database system canidentify other events besides updates to fields of a record. Forexample, an event can be a submission of approval to change a field.Such an event can also have an associated field (e.g., a field showing astatus of whether a change has been submitted). Other examples of eventscan include creation of a record, deletion of a record, converting arecord from one type to another (e.g., converting a lead to anopportunity), closing a record (e.g., a case type record), andpotentially any other state change of a record—any of which couldinclude a field change associated with the state change. Any of theseevents update the record whether by changing a field of the record, astate of the record, or some other characteristic or property of therecord. In one implementation, a list of supported events for creating afeed tracked update can be maintained within the database system, e.g.,at a server or in a database.

In block 320, the database system writes new data to the first record.In one implementation, the new data may include a new value thatreplaces old data. For example, a field is updated with a new value. Inanother implementation, the new data can be a value for a field that didnot contain data before. In yet another implementation, the new datacould be a flag, e.g., for a status of the record, which can be storedas a field of the record.

In some implementations, a “field” can also include records, which arechild objects of the first record in a parent-child hierarchy. A fieldcan alternatively include a pointer to a child record. A child objectitself can include further fields. Thus, if a field of a child object isupdated with a new value, the parent record also can be considered tohave a field changed. In one example, a field could be a list of relatedchild objects, also called a related list.

In block 330, a feed tracked update is generated about the update to therecord. In one implementation, the feed tracked update is created inparts for assembling later into a display version. For example, evententries can be created and tracked in a first table, and changed fieldentries can be tracked in another table that is cross-referenced withthe first table. More specifics of such implementations are providedlater, e.g., with respect to FIG. 9A. In another implementation, thefeed tracked update is automatically generated by the database system.The feed tracked update can convey in words that the first record hasbeen updated and provide details about what was updated in the recordand who performed the update. In some implementations, a feed trackedupdate is generated for only certain types of event and/or updatesassociated with the first record.

In one implementation, a tenant (e.g., through an administrator) canconfigure the database system to create (enable) feed tracked updatesonly for certain types of records. For example, an administrator canspecify that records of designated types such as accounts andopportunities are enabled. When an update (or other event) is receivedfor the enabled record type, then a feed tracked update would begenerated. In another implementation, a tenant can also specify thefields of a record whose changes are to be tracked, and for which feedtracked updates are created. In one aspect, a maximum number of fieldscan be specified for tracking, and may include custom fields. In oneimplementation, the type of change can also be specified, for example,that the value change of a field is to be larger than a threshold (e.g.,an absolute amount or a percentage change). In yet anotherimplementation, a tenant can specify which events are to cause ageneration of a feed tracked update. Also, in one implementation,individual users can specify configurations specific to them, which cancreate custom feeds as described in more detail below.

In one implementation, changes to fields of a child object are nottracked to create feed tracked updates for the parent record. In anotherimplementation, the changes to fields of a child object can be trackedto create feed tracked updates for the parent record. For example, achild object of the parent type can be specified for tracking, andcertain fields of the child object can be specified for tracking. Asanother example, if the child object is of a type specified fortracking, then a tracked change for the child object is propagated toparent records of the child object.

In block 340, the feed tracked update is added to a feed for the firstrecord. In one implementation, adding the feed tracked update to a feedcan include adding events to a table (which may be specific to a recordor be for all or a group of objects), where a display version of a feedtracked update can be generated dynamically and presented in a GUI as afeed item when a user requests a feed for the first record. In anotherimplementation, a display version of a feed tracked update can be addedwhen a record feed is stored and maintained for a record. As mentionedabove, a feed may be maintained for only certain records. In oneimplementation, the feed of a record can be stored in the databaseassociated with the record. For example, the feed can be stored as afield (e.g., as a child object) of the record. Such a field can store apointer to the text to be displayed for the feed tracked update.

In some implementations, only the current feed tracked update (or othercurrent feed item) may be kept or temporarily stored, e.g., in sometemporary memory structure. For example, a feed tracked update for onlya most recent change to any particular field is kept. In otherimplementations, many previous feed tracked updates may be kept in thefeed. A time and/or date for each feed tracked update can be tracked.Herein, a feed of a record is also referred to as an entity feed, as arecord is an instance of a particular entity object of the database.

In block 350, followers of the first record can be identified. Afollower is a user following the first record, such as a subscriber tothe feed of the first record. In one implementation, when a userrequests a feed of a particular record, such an identification of block350 can be omitted. In another implementation where a record feed ispushed to a user (e.g., as part of a news feed), then the user can beidentified as a follower of the first record. Accordingly, this blockcan include the identification of records and other objects beingfollowed by a particular user.

In one implementation, the database system can store a list of thefollowers for a particular record. In various implementations, the listcan be stored with the first record or associated with the record usingan identifier (e.g., a pointer) to retrieve the list. For example, thelist can be stored in a field of the first record. In anotherimplementation, a list of the records that a user is following is used.In one implementation, the database system can have a routine that runsfor each user, where the routine polls the records in the list todetermine if a new feed tracked update has been added to a feed of therecord. In another implementation, the routine for the user can berunning at least partially on a user device, which contacts the databaseto perform the polling.

In block 360, in one implementation, the feed tracked update can bestored in a table, as described in greater detail below. When the useropens a feed, an appropriate query is sent to one or more tables toretrieve updates to records, also described in greater detail below. Insome implementations, the feed shows feed tracked updates in reversechronological order. In one implementation, the feed tracked update ispushed to the feed of a user, e.g., by a routine that determines thefollowers for the record from a list associated with the record. Inanother implementation, the feed tracked update is pulled to a feed,e.g., by a user device. This pulling may occur when a user requests thefeed, as occurs in block 370. Thus, these actions may occur in adifferent order. The creation of the feed for a pull may be a dynamiccreation that identifies records being followed by the requesting user,generates the display version of relevant feed tracked updates fromstored information (e.g., event and field change), and adds the feedtracked updates into the feed. A feed of feed tracked updates of recordsand other objects that a user is following is also generally referred toherein as a news feed, which can be a subset of a larger informationfeed in which other types of information updates appear, such as posts.

In yet another implementation, the feed tracked update could be sent asan email to the follower, instead of in a feed. In one implementation,email alerts for events can enable people to be emailed when certainevents occur. In another implementation, emails can be sent when thereare posts on a user profile and posts on entities to which the usersubscribes. In one implementation, a user can turn on/off email alertsfor all or some events. In an implementation, a user can specify whatkind of feed tracked updates to receive about a record that the user isfollowing. For example, a user can choose to only receive feed trackedupdates about certain fields of a record that the user is following, andpotentially about what kind of update was performed (e.g., a new valueinput into a specified field, or the creation of a new field).

In block 370, a follower can access his/her news feed to see the feedtracked update. In one implementation, the user has just one news feedfor all of the records that the user is following. In one aspect, a usercan access his/her own feed by selecting a particular tab or otherobject on a page of an interface to the database system. Once selectedthe feed can be provided as a list, e.g., with an identifier (e.g., atime) or including some or all of the text of the feed tracked update.In another implementation, the user can specify how the feed trackedupdates are to be displayed and/or sent to the user. For example, a usercan specify a font for the text, a location of where the feed can beselected and displayed, amount of text to be displayed, and other textor symbols to be displayed (e.g., importance flags).

FIG. 4 shows a block diagram of an example of components of a databasesystem configuration 400 performing a method for tracking an update to arecord according to some implementations. Database system configuration400 can perform implementations of method 300, as well asimplementations of other methods described herein.

A first user 405 sends a request 1 to update record 425 in databasesystem 416. Although an update request is described, other events thatare being tracked are equally applicable. In various implementations,the request 1 can be sent via a user interface (e.g., 30 of FIG. 1B) oran application program interface (e.g., API 32). An I/O port 420 canaccommodate the signals of request 1 via any input interface, and sendthe signals to one or more processors 417. The processor 417 can analyzethe request and determine operations to be performed. Herein, anyreference to a processor 417 can refer to a specific processor or anyset of processors in database system 416, which can be collectivelyreferred to as processor 417.

Processor 417 can determine an identifier for record 425, and sendcommands with the new data 2 of the request to record database 412 toupdate record 425. In one implementation, record database 412 is wheretenant storage space 112 of FIG. 1B is located. The request 1 and newdata commands 2 can be encapsulated in a single write transaction sentto record database 412. In one implementation, multiple changes torecords in the database can be made in a single write transaction.

Processor 417 can also analyze request 1 to determine whether a feedtracked update is to be created, which at this point may includedetermining whether the event (e.g., a change to a particular field) isto be tracked. This determination can be based on an interaction (i.e.,an exchange of data) with record database 412 and/or other databases, orbased on information stored locally (e.g., in cache or RAM) at processor417. In one implementation, a list of record types that are beingtracked can be stored. The list may be different for each tenant, e.g.,as each tenant may configure the database system to its ownspecifications. Thus, if the record 425 is of a type not being tracked,then the determination of whether to create a feed tracked update canstop there.

The same list or a second list (which can be stored in a same locationor a different location) can also include the fields and/or events thatare tracked for the record types in the first list. This list can besearched to determine if the event is being tracked. A list may alsocontain information having the granularity of listing specific recordsthat are to be tracked (e.g., if a tenant can specify the particularrecords to be tracked, as opposed to just type).

As an example, processor 417 may obtain an identifier associated withrecord 425 (e.g., obtained from request 1 or database 412), potentiallyalong with a tenant identifier, and cross-reference the identifier witha list of records for which feed tracked updates are to be created.Specifically, the record identifier can be used to determine the recordtype and a list of tracked types can be searched for a match. Thespecific record may also be checked if such individual record trackingwas enabled. The name of the field to be changed can also be used tosearch a list of tracking-enabled fields. Other criteria besides fieldand events can be used to determine whether a feed tracked update iscreated, e.g., type of change in the field. If a feed tracked update isto be generated, processor 417 can then generate the feed trackedupdate.

In some implementations, a feed tracked update is created dynamicallywhen a feed (e.g., the entity feed of record 425) is requested. Thus, inone implementation, a feed tracked update can be created when a userrequests the entity feed for record 425. In this implementation, thefeed tracked update may be created (e.g., assembled), includingre-created, each time the entity feed is to be displayed to any user. Inone implementation, one or more event history tables can keep track ofprevious events so that the feed tracked update can be re-created.

In another implementation, a feed tracked update can be created at thetime the event occurs, and the feed tracked update can be added to alist of feed items. The list of feed items may be specific to record425, or may be an aggregate of feed items including feed items for manyrecords. Such an aggregate list can include a record identifier so thatthe feed items for the entity feed of record 425 can be easilyretrieved. For example, after the feed tracked update has beengenerated, processor 417 can add the new feed tracked update 3 to a feedof record 425. As mentioned above, in one implementation, the feed canbe stored in a field (e.g., as a child object) of record 425. In anotherimplementation, the feed can be stored in another location or in anotherdatabase, but with a link (e.g., a connecting identifier) to record 425.The feed can be organized in various ways, e.g., as a linked list, anarray, or other data structure.

A second user 430 can access the new feed tracked update 3 in variousways. In one implementation, second user 430 can send a request 4 forthe record feed. For example, second user 430 can access a home page(detail page) of the record 425 (e.g., with a query or by browsing), andthe feed can be obtained through a tab, button, or other activationobject on the page. The feed can be displayed on the screen ordownloaded.

In another implementation, processor 417 can add the new feed trackedupdate 5 to a feed (e.g., a news feed) of a user that is followingrecord 425. In one implementation, processor 417 can determine each ofthe followers of record 425 by accessing a list of the users that havebeen registered as followers. This determination can be done for eachnew event (e.g., update 1). In another implementation, processor 417 canpoll (e.g., with a query) the records that second user 430 is followingto determine when new feed tracked updates (or other feed items) areavailable. Processor 417 can use a follower profile 435 of second user430 that can contain a list of the records that the second user 430 isfollowing. Such a list can be contained in other parts of the databaseas well. Second user 430 can then send a request 6 to his/her profile435 to obtain a feed, which contains the new feed tracked update. Theuser's profile 435 can be stored in a profile database 414, which can bethe same or different than database 412.

In some implementations, a user can define a news feed to include newfeed tracked updates from various records, which may be limited to amaximum number. In one implementation, each user has one news feed. Inanother implementation, the follower profile 435 can include thespecifications of each of the records to be followed (with the criteriafor what feed tracked updates are to be provided and how they aredisplayed), as well as the feed.

Some implementations can provide various types of record (entity) feeds.Entity Feeds can exist for record types like account, opportunity, case,and contact. An entity feed can tell a user about the actions thatpeople have taken on that particular record or on one its relatedrecords. The entity feed can include who made the action, which fieldwas changed, and the old and new values. In one implementation, entityfeeds can exist on all supported records as a list that is linked to thespecific record. For example, a feed could be stored in a field thatallows lists (e.g., linked lists) or as a child object.

IV. Tracking Actions of a User

In addition to knowing about events associated with a particular record,it can be helpful for a user to know what a particular user is doing. Inparticular, it might be nice to know what the user is doing without theuser having to generate the feed tracked update (e.g., a user submittinga synopsis of what the user has done). Accordingly, implementations canautomatically track actions of a user that trigger events, and feedtracked updates can be generated for certain events.

FIG. 5 shows a flowchart of an example of a method 500 for trackingactions of a user of a database system, performed in accordance withsome implementations. Method 500 may be performed in addition to method300. The operations of method 300, including order of blocks, can beperformed in conjunction with method 500 and other methods describedherein. Thus, a feed can be composed of changes to a record and actionsof users.

In block 510, a database system (e.g., 16 of FIGS. 1A and 1B) identifiesan action of a first user. In one implementation, the action triggers anevent, and the event is identified. For example, the action of a userrequesting an update to a record can be identified, where the event isreceiving a request or is the resulting update of a record. The actionmay thus be defined by the resulting event. In another implementation,only certain types of actions (events) are identified. Which actions areidentified can be set as a default or can be configurable by a tenant,or even configurable at a user level. In this way, processing effort canbe reduced since only some actions are identified.

In block 520, it is determined whether the event qualifies for a feedtracked update. In one implementation, a predefined list of events(e.g., as mentioned herein) can be created so that only certain actionsare identified. In one implementation, an administrator (or other user)of a tenant can specify the type of actions (events) for which a feedtracked update is to be generated. This block may also be performed formethod 300.

In block 530, a feed tracked update is generated about the action. In anexample where the action is an update of a record, the feed trackedupdate can be similar or the same as the feed tracked update created forthe record. The description can be altered though to focus on the useras opposed to the record. For example, “John D. has closed a newopportunity for account XYZ” as opposed to “an opportunity has beenclosed for account XYZ.”

In block 540, the feed tracked update is added to a profile feed of thefirst user when, e.g., the user clicks on a tab to open a page in abrowser program displaying the feed. In one implementation, a feed for aparticular user can be accessed on a page of the user's profile, in asimilar manner as a record feed can be accessed on a detail page of therecord. In another implementation, the first user may not have a profilefeed and the feed tracked update may just be stored temporarily beforeproceeding. A profile feed of a user can be stored associated with theuser's profile. This profile feed can be added to a news feed of anotheruser.

In block 550, followers of the first user are identified. In oneimplementation, a user can specify which type of actions other users canfollow. Similarly, in one implementation, a follower can select whatactions by a user the follower wants to follow. In an implementationwhere different followers follow different types of actions, which usersare followers of that user and the particular action can be identified,e.g., using various lists that track what actions and criteria are beingfollowed by a particular user. In various implementations, the followersof the first user can be identified in a similar manner as followers ofa record, as described above for block 350.

In block 560, the feed tracked update is added to a news feed of eachfollower of the first user when, e.g., the follower clicks on a tab toopen a page displaying the news feed. The feed tracked update can beadded in a similar manner as the feed items for a record feed. The newsfeed can contain feed tracked updates both about users and records. Inanother implementation, a user can specify what kind of feed trackedupdates to receive about a user that the user is following. For example,a user could specify feed tracked updates with particular keywords, ofcertain types of records, of records owned or created by certain users,particular fields, and other criteria as mentioned herein.

In block 570, a follower accesses the news feed and sees the feedtracked update. In one implementation, the user has just one news feedfor all of the records that the user is following. In anotherimplementation, a user can access his/her own feed (i.e. feed abouthis/her own actions) by selecting a particular tab or other object on apage of an interface to the database system. Thus, a feed can includefeed tracked updates about what other users are doing in the databasesystem. When a user becomes aware of a relevant action of another user,the user can contact the co-worker, thereby fostering teamwork.

V. Generation of a Feed Tracked Update

As described above, some implementations can generate text describingevents (e.g., updates) that have occurred for a record and actions by auser that trigger an event. A database system can be configured togenerate the feed tracked updates for various events in various ways.

In one implementation, the feed tracked update is a grammaticalsentence, thereby being easily understandable by a person. In anotherimplementation, the feed tracked update provides detailed informationabout the update. In various examples, an old value and new value for afield may be included in the feed tracked update, an action for theupdate may be provided (e.g., submitted for approval), and the names ofparticular users that are responsible for replying or acting on the feedtracked update may be also provided. The feed tracked update can alsohave a level of importance based on settings chosen by theadministrator, a particular user requesting an update, or by a followinguser who is to receive the feed tracked update, which fields is updated,a percentage of the change in a field, the type of event, or anycombination of these factors.

The system may have a set of heuristics for creating a feed trackedupdate from the event (e.g., a request to update). For example, thesubject may be the user, the record, or a field being added or changed.The verb can be based on the action requested by the user, which can beselected from a list of verbs (which may be provided as defaults orinput by an administrator of a tenant). In one implementation, feedtracked updates can be generic containers with formatting restrictions,

As an example of a feed tracked update for a creation of a new record,“Mark Abramowitz created a new Opportunity for IBM-20,000 laptops withAmount as $3.5M and Sam Palmisano as Decision Maker.” This event can beposted to the profile feed for Mark Abramowitz and the entity feed forrecord of Opportunity for IBM-20,000 laptops. The pattern can be givenby (AgentFullName) created a new (ObjectName)(RecordName) with[(FieldName) as (FieldValue) [, / and] ]* [[added / changed / removed](RelatedListRecordName) [as / to / as] (RelatedListRecordValue) [, /and] ]. Similar patterns can be formed for a changed field (standard orcustom) and an added child record to a related list.

VI. Tracking Commentary from or about a User

Some implementations can also have a user submit text, instead of thedatabase system generating a feed tracked update. As the text issubmitted as part or all of a message by a user, the text can be aboutany topic. Thus, more information than just actions of a user and eventsof a record can be conveyed. In one implementation, the messages can beused to ask a question about a particular record, and users followingthe record can provide comments and responses.

FIG. 6 shows a flowchart of an example of a method 600 for creating anews feed from messages created by a user about a record or anotheruser, performed in accordance with some implementations. In oneimplementation, method 600 can be combined with methods 300 and 500. Inone aspect, a message can be associated with the first user when thefirst user creates the message (e.g., a post or comment about a recordor another user). In another aspect, a message can be associated withthe first user when the message is about the first user (e.g., posted byanother user on the first user's profile feed).

In block 610, the database system receives a message (e.g., a post orstatus update) associated with a first user. The message (e.g., a postor status update) can contain text and/or multimedia content submittedby another user or by the first user. In one implementation, a post isfor a section of the first user's profile page where any user can add apost, and where multiple posts can exist. Thus, a post can appear on thefirst user's profile page and can be viewed when the first user'sprofile is visited. For a message about a record, the post can appear ona detail page of a record. Note the message can appear in other feeds aswell. In another implementation, a status update about the first usercan only be added by the first user. In one implementation, a user canonly have one status message.

In block 620, the message is added to a table, as described in greaterdetail below. When the feed is opened, a query filters one or moretables to identify the first user, identify other persons that the useris following, and retrieve the message. Messages and record updates arepresented in a combined list as the feed. In this way, in oneimplementation, the message can be added to a profile feed of the firstuser, which is associated (e.g., as a related list) with the firstuser's profile. In one implementation, the posts are listedindefinitely. In another implementation, only the most recent posts(e.g., last 50) are kept in the profile feed. Such implementations canalso be employed with feed tracked updates. In yet anotherimplementation, the message can be added to a profile of the user addingthe message.

In block 630, the database system identifies followers of the firstuser. In one implementation, the database system can identify thefollowers as described above for method 500. In various implementations,a follower can select to follow a feed about the actions of the firstuser, messages about the first user, or both (potentially in a samefeed).

In block 640, the message is added to a news feed of each follower. Inone implementation, the message is only added to a news feed of aparticular follower if the message matches some criteria, e.g., themessage includes a particular keyword or other criteria. In anotherimplementation, a message can be deleted by the user who created themessage. In one implementation, once deleted by the author, the messageis deleted from all feeds to which the message had been added.

In block 650, the follower accesses a news feed and sees the message.For example, the follower can access a news feed on the follower's ownprofile page. As another example, the follower can have a news feed sentto his/her own desktop without having to first go to a home page.

In block 660, the database system receives a comment about the message.The database system can add the comment to a feed of the same firstuser, much as the original message was added. In one implementation, thecomment can also be added to a feed of a second user who added thecomment. In one implementation, users can also reply to the comment. Inanother implementation, users can add comments to a feed tracked update,and further comments can be associated with the feed tracked update. Inyet another implementation, making a comment or message is not an actionto which a feed tracked update is created. Thus, the message may be theonly feed item created from such an action.

In one implementation, if a feed tracked update or post is deleted, itscorresponding comments are deleted as well. In another implementation,new comments on a feed tracked update or post do not update the feedtracked update timestamp. Also, the feed tracked update or post cancontinue to be shown in a feed (profile feed, record feed, or news feed)if it has had a comment within a specified timeframe (e.g., within thelast week). Otherwise, the feed tracked update or post can be removed inan implementation.

In some implementations, all or most feed tracked updates can becommented on. In other implementations, feed tracked updates for certainrecords (e.g., cases or ideas) are not commentable. In variousimplementations, comments can be made for any one or more records ofopportunities, accounts, contacts, leads, and custom objects.

In block 670, the comment is added to a news feed of each follower. Inone implementation, a user can make the comment within the user's newsfeed. Such a comment can propagate to the appropriate profile feed orrecord feed, and then to the news feeds of the following users. Thus,feeds can include what people are saying, as well as what they aredoing. In one aspect, feeds are a way to stay up-to-date (e.g., onusers, opportunities, etc.) as well as an opportunity to reach out toco-workers/partners and engage them around common goals.

In some implementations, users can rate feed tracked updates or messages(including comments). A user can choose to prioritize a display of afeed so that higher rated feed items show up higher on a display. Forexample, in an implementation where comments are answers to a specificquestion, users can rate the different status posts so that a bestanswer can be identified. As another example, users are able to quicklyidentify feed items that are most important as those feed items can bedisplayed at a top of a list. The order of the feed items can be basedon an importance level (which can be determined by the database systemusing various factors, some of which are mentioned herein) and based ona rating from users. In one implementation, the rating is on a scalethat includes at least 3 values. In another implementation, the ratingis based on a binary scale.

Besides a profile for a user, a group can also be created. In variousimplementations, the group can be created based on certain attributesthat are common to the users, can be created by inviting users, and/orcan be created by receiving requests to join from a user. In oneimplementation, a group feed can be created, with messages being addedto the group feed when someone submits a message to the group as a wholethrough a suitable user interface. For example, a group page may have agroup feed or a section within the feed for posts, and a user can submita post through a publisher component in the user interface by clickingon a “Share” or similar button. In another implementation, a message canbe added to a group feed when the message is submitted about any one ofthe members. Also, a group feed can include feed tracked updates aboutactions of the group as a whole (e.g., when an administrator changesdata in a group profile or a record owned by the group), or aboutactions of an individual member.

FIG. 7 shows an example of a group feed on a group page according tosome implementations. As shown, a feed item 710 shows that a user hasposted a document to the group object. The text “Bill Bauer has postedthe document Competitive Insights” can be generated by the databasesystem in a similar manner as feed tracked updates about a record beingchanged. A feed item 720 shows a post to the group, along with comments730 from Ella Johnson, James Saxon, Mary Moore and Bill Bauer.

FIG. 8 shows an example of a record feed containing a feed trackedupdate, post, and comments according to some implementations. Feed item810 shows a feed tracked update based on the event of submitting adiscount for approval. Other feed items show posts, e.g., from BillBauer, that are made to the record and comments, e.g., from Erica Lawand Jake Rapp, that are made on the posts.

Vii. Infrastructure for a Feed

A. Tables Used to Create a Feed

FIG. 9A shows an example of a plurality of feed tracked update tablesthat may be used in tracking events and creating feeds according to someimplementations. The tables of FIG. 9A may have entries added, orpotentially removed, as part of tracking events in the database fromwhich feed items are creates or that correspond to feed items. In oneimplementation, each tenant has its own set of tables that are createdbased on criteria provided by the tenant.

An event history table 910 can provide a feed tracked update of eventsfrom which feed items are created. In one aspect, the events are forobjects that are being tracked. Thus, table 910 can store and changefeed tracked updates for feeds, and the changes can be persisted. Invarious implementations, event history table 910 can have columns ofevent ID 911, object ID 912 (also called parent ID), and created by ID913. The event ID 911 can uniquely identify a particular event and canstart at 1 (or other number or value).

Each new event can be added chronologically with a new event ID, whichmay be incremented in order. An object ID 912 can be used to track whichrecord or user's profile is being changed. For example, the object IDcan correspond to the record whose field is being changed or the userwhose feed is receiving a post. The created by ID 913 can track the userwho is performing the action that results in the event, e.g., the userthat is changing the field or that is posting a message to the profileof another user.

In one implementation, a name of an event can also be stored in table910. In one implementation, a tenant can specify events that they wanttracked. In an implementation, event history table 910 can include thename of the field that changed (e.g., old and new values). In anotherimplementation, the name of the field, and the values, are stored in aseparate table. Other information about an event (e.g., text of comment,feed tracked update, post or status update) can be stored in eventhistory table 910, or in other tables, as is now described.

A field change table 920 can provide a feed tracked update of thechanges to the fields. The columns of table 920 can include an event ID921 (which correlates to the event ID 911), an old value 922 for thefield, and the new value 923 for the field. In one implementation, if anevent changes more than one field value, then there can be an entry foreach field changed. As shown, event ID 921 has two entries for eventE37.

A comment table 930 can provide a feed tracked update of the commentsmade regarding an event, e.g., a comment on a post or a change of afield value. The columns of table 930 can include an event ID 921 (whichcorrelates to the event ID 911), the comment column 932 that stores thetext of the comment, and the time/date 933 of the comment. In oneimplementation, there can be multiple comments for each event. As shown,event ID 921 has two entries for event E37.

A user subscription table 940 can provide a list of the objects beingfollowed (subscribed to) by a user. In one implementation, each entryhas a user ID 941 of the user doing the following and one object ID 942corresponding to the object being followed. In one implementation, theobject being followed can be a record or a user. As shown, the user withID U819 is following object IDs O615 and O489. If user U819 is followingother objects, then additional entries may exist for user U819. Also asshown, user U719 is also following object O615. The user subscriptiontable 940 can be updated when a user adds or deletes an object that isbeing followed.

In one implementation, regarding a profile feed and a news feed, theseare read-only views on the event history table 910 specialized for thesefeed types. Conceptually the news feed can be a semi-join between theuser subscription table 940 and the event history table 910 on theobject IDs 912 and 942 for the user. In one aspect, these entities canhave polymorphic parents and can be subject to a number of restrictionsdetailed herein, e.g., to limit the cost of sharing checks.

In one implementation, entity feeds are modeled in the API as a feedassociate entity (e.g., AccountFeed, CaseFeed, etc). A feed associateentity includes information composed of events (e.g., event IDs) foronly one particular record type. Such a list can limit the query (andsharing checks) to a specific record type. In one aspect, thisstructuring of the entity feeds can make the query run faster. Forexample, a request for a feed of a particular account can include therecord type of account. In one implementation, an account feed table canthen be searched, where the table has account record IDs andcorresponding event IDs or pointers to particular event entries in eventhistory table 910. Since the account feed table only contains some ofthe records (not all), the query can run faster.

In one implementation, there may be objects with no events listed in theevent history table 910, even though the record is being tracked. Inthis case, the database service can return a result indicating that nofeed items exist.

A feed item can represent an individual field change of a record,creation and deletion of a record, or other events being tracked for arecord or a user. In one implementation, all of the feed items in asingle transaction (event) can be grouped together and have the sameevent ID. A single transaction relates to the operations that can beperformed in a single communication with the database. In anotherimplementation where a feed is an object of the database, a feed itemcan be a child of a profile feed, news feed, or entity feed. If a feeditem is added to multiple feeds, the feed item can be replicated as achild of each feed to which the feed item is added.

In some implementations, a comment exists as an item that depends fromfeed tracked updates, posts, status updates, and other items that areindependent of each other. Thus, a feed comment object can exist as achild object of a feed item object. For example, comment table 930 canbe considered a child table of event history table 910. In oneimplementation, a feed comment can be a child of a profile feed, newsfeed, or entity feed that is separate from other feed items.

In one implementation, viewing a feed pulls up the most recent messagesor feed tracked updates (e.g., 25) and searches the most recent (e.g.,4) comments for each feed item. The comments can be identified via thecomment table 930. In one implementation, a user can request to see morecomments, e.g., by selecting a see more link.

After feed items have been generated, they can be filtered so that onlycertain feed items are displayed, which may be tailored to a specifictenant and/or user. In one implementation, a user can specify changes toa field that meet certain criteria for the feed item to show up in afeed displayed to the user, e.g., a news feed or even an entity feeddisplayed directly to the user. In one implementation, the criteria canbe combined with other factors (e.g., number of feed items in the feed)to determine which feed items to display. For instance, if a smallnumber of feed items exist (e.g., below a threshold), then all of thefeed items may be displayed.

In one implementation, a user can specify the criteria via a query onthe feed items in his/her new feed, and thus a feed may only returnobjects of a certain type, certain types of events, feed tracked updatesabout certain fields, and other criteria mentioned herein. Messages canalso be filtered according to some criteria, which may be specified in aquery. Such an added query can be added onto a standard query that isused to create the news feed for a user. A first user could specify theusers and records that the first user is following in this manner, aswell as identify the specific feed items that the first user wants tofollow. The query could be created through a graphical interface oradded by a user directly in a query language. Other criteria couldinclude receiving only posts directed to a particular user or record, asopposed to other feed items.

In one implementation, a user can access a feed of a record if the usercan access the record. The security rules for determining whether a userhas access to a record can be performed in a variety of ways, some ofwhich are described in commonly assigned U.S. Pat. No. 8,095,531, titledMETHODS AND SYSTEMS FOR CONTROLLING ACCESS TO CUSTOM OBJECTS IN ADATABASE, by Weissman et al., issued on Jan. 10, 2012, and herebyincorporated by reference in its entirety and for all purposes.

In one implementation, a user can edit a feed of a record if the userhas access to the record, e.g., deleting or editing a feed item. Inanother implementation, a user (besides an administrator) cannot edit afeed item, except for performing an action from which a feed item can becreated. In one example, a user is first has to have access to aparticular record and field for a feed item to be created based on anaction of the user. In this case, an administrator can be considered tobe a user with MODIFY-ALL-DATA security level. In yet anotherimplementation, a user who created the record can edit the feed.

In one implementation, the text of posts are stored in a child table(post table 950), which can be cross-referenced with event history table910. Post table 950 can include event ID 951 (to cross-reference withevent ID 911), post text 952 to store the text of the post, andtime/date 953. An entry in post table 950 can be considered a feed postobject.

VIII. Subscribing to Users and Records to Follow

As described above, a user can follow users, groups, and records.Implementations can provide mechanisms for a user to manage which users,groups, and records that the user is currently following. In oneimplementation, a user can be limited to the number of users and records(collectively or separately) that the user can follow. For example, auser may be restricted to only following 10 users and 15 records, or asanother example, 25 total. Alternatively, the user may be permitted tofollow more or less users.

In one implementation, a user can go to a page of a record and thenselect to follow that object (e.g., with a button marked “follow” or“join”). In another implementation, a user can search for a record andhave the matching records show up in a list. The search can includecriteria of records that the user might want to follow. Such criteriacan include the owner, the creation date, last comment date, andnumerical values of particular fields (e.g., an opportunity with a valueof more than $10,000).

A follow button (or other activation object) can then reside next toeach record in the resulting list, and the follow button can be selectedto start following the record. Similarly, a user can go to a profilepage of a user and select to follow the user, or a search for users canprovide a list, where one or more users can be selected for followingfrom the list. The selections of subscribing and unsubscribing can addand delete rows in table 920.

In some implementations, a subscription center acts as a centralizedplace in a database application (e.g., application platform 18) tomanage which records a user subscribes to, and which field updates theuser wants to see in feed tracked updates. The subscription center canuse a subscription table to keep track of the subscriptions of varioususers. In one implementation, the subscription center shows a list ofall the items (users and records) a user is subscribed to. In anotherimplementation, a user can unsubscribe to subscribed objects from thesubscription center.

A. Automatic Subscription

FIG. 9B shows a flowchart of an example of a method 900 forautomatically subscribing a user to an object in a database system,performed in accordance with some implementations. Any of the followingblocks can be performed wholly or partially with the database system,and in particular by one or more processor of the database system.

In block 901, one or more properties of an object stored in the databasesystem are received. The properties can be received from administratorsof the database system, or from users of the database system (which maybe an administrator of a customer organization). The properties can berecords or users, and can include any of the fields of the object thatare stored in the database system. Examples of properties of a recordinclude: an owner of the record, a user that converted the record fromone record type to another record type, whether the first user hasviewed the record, and a time the first user viewed the record. Examplesof properties of a user include: which organization (tenant) the user isassociated with, the second user's position in the same organization,and which other users the user had emailed or worked with on projects.

In block 902, the database system receives one or more criteria aboutwhich users are to automatically follow the object. Examples of thecriteria can include: an owner or creator of a record is to follow therecord, subordinates of an owner or creator of a record are to followthe record, and a user is to follow his/her manager, the user's peers,other users in the same business group as the user, and other users thatthe user has emailed or worked with on a project. The criteria can bespecific to a user or group of users (e.g., users of a tenant).

In block 903, the database system determines whether the one or moreproperties of the object satisfy the one or more criteria for a firstuser. In one implementation, this determination can occur by firstobtaining the criteria and then determining objects that satisfy thecriteria. The determination can occur periodically, at time of creationof an object, or at other times.

In block 904, if the criteria are satisfied, the object is associatedwith the first user. The association can be in a list that storesinformation as to what objects are being followed by the first user.User subscription table 940 is an example of such a list. In oneimplementation, the one or more criteria are satisfied if one propertysatisfies at least one criterion. Thus, if the criteria are that a userfollows his/her manager and the object is the user's manager, then thefirst user will follow the object.

In one implementation, a user can also be automatically unsubscribed,e.g., if a certain action happens. The action could be a change in theuser's position within the organization, e.g., a demotion or becoming acontractor. As another example, if a case gets closed, then usersfollowing the case may be automatically unsubscribed.

IX. Adding Items to a Feed

As described above, a feed includes feed items, which include feedtracked updates and messages, as defined herein. Various feeds can begenerated. For example, a feed can be generated about a record or abouta user. Then, users can view these feeds. A user can separately view afeed of a record or user, e.g., by going to a home page for the user orthe record. As described above, a user can also follow another user orrecord and receive the feed items of those feeds through a separate feedapplication. The feed application can provide each of the feeds that auser is following and, in some examples, can combine various feeds in asingle information feed.

A feed generator can refer to any software program running on aprocessor or a dedicated processor (or combination thereof) that cangenerate feed items (e.g., feed tracked updates or messages) and combinethem into a feed. In one implementation, the feed generator can generatea feed item by receiving a feed tracked update or message, identifyingwhat feeds the item should be added to, and adding the feed. Adding thefeed can include adding additional information (metadata) to the feedtracked update or message (e.g., adding a document, sender of message, adetermined importance, etc.). The feed generator can also check to makesure that no one sees feed tracked updates for data that they don't haveaccess to see (e.g., according to sharing rules). A feed generator canrun at various times to pre-compute feeds or to compute themdynamically, or combinations thereof.

In one implementation, processor 417 in FIG. 4 can identify an eventthat meets criteria for a feed tracked update, and then generate thefeed tracked update. Processor 417 can also identify a message. Forexample, an application interface can have certain mechanisms forsubmitting a message (e.g., “submit” buttons on a profile page, detailpage of a record, “comment” button on post), and use of these mechanismscan be used to identify a message to be added to a table used to createa feed or added directly to a list of feed items ready for display.

A. Adding Items to a Pre-Computed Feed

In some implementations, a feed of feed items is created before a userrequests the feed. Such an implementation can run fast, but have highoverall costs for storage. In one implementation, once a profile feed ora record feed has been created, a feed item (messages and feed trackedupdates) can be added to the feed. The feed can exist in the databasesystem in a variety of ways, such as a related list. The feed caninclude mechanisms to remove items as well as add them.

As described above, a news feed can be an aggregated feed of all therecord feeds and profile feeds to which a user has subscribed. The newsfeed can be provided on the home page of the subscribing user.Therefore, a news feed can be created by and exist for a particularuser. For example, a user can subscribe to receive entity feeds ofcertain records that are of interest to the user, and to receive profilefeeds of people that are of interest (e.g., people on a same team, thatwork for the user, are a boss of the user, etc.). A news feed can tell auser about all the actions across all the records (and people) whom haveexplicitly (or implicitly) been subscribed to via the subscriptionscenter (described above).

In one implementation, only one instance of each feed tracked update isshown on a user's news feed, even if the feed tracked update ispublished in multiple entities to which the user is subscribed. In oneaspect, there may be delays in publishing news articles. For example,the delay may be due to queued up messages for asynchronous entity feedtracked update persistence. Different feeds may have different delays(e.g., delay for new feeds, but none of profile and entity feeds). Inanother implementation, certain feed tracked updates regarding asubscribed profile feed or an entity feed are not shown because the useris not allowed access, e.g., due to sharing rules (which restrict whichusers can see which data). Also, in one implementation, data of therecord that has been updated (which includes creation) can be providedin the feed (e.g., a file or updated value of a feed can be added as aflash rendition).

B. Dynamically Generating Feeds

In some implementations, a feed generator can generate the feed itemsdynamically when a user requests to see a particular feed, e.g., aprofile feed, entity feed, or the user's news feed. In oneimplementation, the most recent feed items (e.g., top 50) are generatedfirst. In one aspect, the other feed items can be generated as abackground process, e.g., not synchronously with the request to view thefeed. However, since the background process is likely to complete beforea user gets to the next 50 feed items, the feed generation may appearsynchronous. In another aspect, the most recent feed items may or maynot include comments, e.g., that are tied to feed tracked updates orposts.

In one implementation, the feed generator can query the appropriatesubset of tables shown in FIG. 9A and/or other tables as necessary, togenerate the feed items for display. For example, the feed generator canquery the event history table 910 for the updates that occurred for aparticular record. The ID of the particular record can be matchedagainst the ID of the record. In one implementation, changes to a wholeset of records can be stored in one table. The feed generator can alsoquery for status updates, posts, and comments, each of which can bestored in different parts of a record or in separate tables, as shown inFIG. 9A. What gets recorded in the entity event history table (as wellas what is displayed) can be controlled by a feed settings page insetup, which can be configurable by an administrator and can be the samefor the entire organization, as is described above for custom feeds.

In one implementation, there can be two feed generators. For example,one generator can generate the record and profile feeds and anothergenerator can generate news feeds. For the former, the feed generatorcan query identifiers of the record or the user profile. For the latter,the news feed generator can query the subscribed profile feeds andrecord feeds, e.g., user subscription table 940. In one implementation,the feed generator looks at a person's subscription center to decidewhich feeds to query for and return a list of feed items for the user.The list can be de-duped, e.g., by looking at the event number andvalues for the respective table, such as field name or ID, comment ID,or other information.

C. Adding Information to Feed Tracked Update Tables

FIG. 10 shows a flowchart of an example of a method 1000 for savinginformation to feed tracking tables, performed in accordance with someimplementations. In one implementation, some of the blocks may beperformed regardless of whether a specific event or part of an event(e.g., only one field of an update is being tracked) is being tracked.In various implementations, a processor or set of processors (hardwiredor programmed) can perform method 1000 and any other method describedherein.

In block 1010, data indicative of an event is received. The data mayhave a particular identifier that specifies the event. For example,there may be a particular identifier for a field update. In anotherimplementation, the transaction may be investigated for keywordsidentifying the event (e.g., terms in a query indicating a close, changefield, or create operations).

In block 1020, it is determined whether the event is being tracked forinclusion into feed tracked update tables. The determination of what isbeing tracked can be based on a tenant's configuration as describedabove. In one aspect, the event has an actor (person performing anevent), and an object of the event (e.g., record or user profile beingchanged).

In block 1030, the event is written to an event history table (e.g.,table 910). In one implementation, this feed tracking operation can beperformed in the same transaction that performs a save operation forupdating a record. In another implementation, a transaction includes atleast two roundtrip database operations, with one roundtrip being thedatabase save (write), and the second database operation being thesaving of the update in the feed tracked update table. In oneimplementation, the event history table is chronological. In anotherimplementation, if user A posts on user B's profile, then user A isunder the “created by” 913 and user B is under the object ID 912.

In block 1040, a field change table (e.g., field change table 920) canbe updated with an entry having the event identifier and fields thatwere changed in the update. In one implementation, the field changetable is a child table of the event history table. This table caninclude information about each of the fields that are changed. Forexample, for an event that changes the name and balance for an accountrecord, an entry can have the event identifier, the old and new name,and the old and new balance. Alternatively, each field change can be ina different row with the same event identifier. The field name or ID canalso be included to determine which field the values are associated.

In block 1050, when the event is a post, a post table (e.g., post table950) can be updated with an entry having the event identifier and textof the post. In one implementation, the field change table is a childtable of the event history table. In another implementation, the textcan be identified in the transaction (e.g., a query command), strippedout, and put into the entry at the appropriate column. The varioustables described herein can be combined or separated in various ways.For example, the post table and the field change table may be part ofthe same table or distinct tables, or may include overlapping portionsof data.

In block 1060, a comment is received for an event and the comment isadded to a comment table (e.g., comment table 930). The comment could befor a post or an update of a record, from which a feed tracked updatecan be generated for display. In one implementation, the text can beidentified in the transaction (e.g., a query command), stripped out, andput into the entry at the appropriate column.

D. Reading Information from Feed Tracked Update Tables

FIG. 11 shows a flowchart of an example of a method 1100 for reading afeed item as part of generating a feed for display, performed inaccordance with some implementations. In one implementation, the feeditem may be read as part of creating a feed for a record.

In block 1110, a query is received for an events history table (e.g.,event history table 910) for events related to a particular record. Inone implementation, the query includes an identifier of the record forwhich the feed is being requested. In various implementations, the querymay be initiated from a detail page of the record, a home page of a userrequesting the record feed, or from a listing of different records(e.g., obtained from a search or from browsing).

In block 1120, the user's security level can be checked to determine ifthe user can view the record feed. Typically, a user can view a recordfeed, if the user can access the record. This security check can beperformed in various ways. In one implementation, a first table ischecked to see if the user has a classification (e.g., a security levelthat allows him to view records of the given type). In anotherimplementation, a second table is checked to see if the user is allowedto see the specific record. The first table can be checked before thesecond table, and both tables can be different sections of a same table.If the user has requested the feed from the detail page of the record,one implementation can skip the security level check for the recordsince the check was already done when the user requested to view thedetail page.

In one implementation, a security check is determined upon each requestto view the record feed. Thus, whether or not a feed item is displayedto a user is determined based on access rights, e.g., when the userrequests to see a feed of a record or a news feed of all the objects theuser is following. In this manner, if a user's security changes, a feedautomatically adapts to the user's security level when it is changed. Inanother implementation, a feed can be computed before being requestedand a subsequent security check can be made to determine whether theperson still has access right to view the feed items. The security(access) check may be at the field level, as well as at the recordlevel.

In block 1130, if the user can access the record, a field level securitytable can be checked to determine whether the user can see particularfields. In one implementation, only those fields are displayed to theuser. Alternatively, a subset of those the user has access to isdisplayed. The field level security check may optionally be performed atthe same time and even using the same operation as the record levelcheck. In addition, the record type check may also be performed at thistime. If the user can only see certain fields, then any feed itemsrelated to those fields (e.g., as determined from field change table920) can be removed from the feed being displayed.

In block 1140, the feed items that the user has access to are displayed.In one implementation, a predetermined number (e.g., 20) of feed itemsare displayed at a time. The method can display the first 20 feed itemsthat are found to be readable, and then determine others while the useris viewing the first 20. In another implementation, the other feed itemsare not determined until the user requests to see them, e.g., byactivating a see more link.

FIG. 12 shows a flowchart of an example of a method 1200 for reading afeed item of a profile feed for display, performed in accordance withsome implementations. In one implementation, the query includes anidentifier of the user profile feed that is being requested. Certainblocks may be optional, as is also true for other methods describedherein. For example, security checks may not be performed.

In block 1210, a query is directed to an event history table (e.g.,event history table 910) for events having a first user as the actor ofthe event (e.g., creation of an account) or on which the event occurred(e.g., a post to the user's profile). In various implementations, thequery may be initiated by a second user from the user's profile page, ahome page of a user requesting the profile feed (e.g., from a list ofusers being followed), or from a listing of different users (e.g.,obtained from a search or from browsing). Various mechanisms fordetermining aspects of events and obtaining information from tables canbe the same across any of the methods described herein.

In block 1220, a security check may also be performed on whether thesecond user can see the first user's profile. In one implementation anyuser can see the profile of another user of the same tenant, and block1220 is optional.

In block 1230, a security (access) check can be performed for the feedtracked updates based on record types, records, and/or fields, as wellsecurity checks for messages. In one implementation, only the feedtracked updates related to records that the person has updated are theones that need security check as the feed items about the user arereadable by any user of the same tenant. Users of other tenants are notnavigable, and thus security can be enforced at a tenant level. Inanother implementation, messages can be checked for keywords or links toa record or field that the second user does not have access.

As users can have different security classifications, it is importantthat a user with a low-level security cannot see changes to records thathave been performed by a user with high-level security. In oneimplementation, each feed item can be checked and then the viewableresults displayed, but this can be inefficient. For example, such asecurity check may take a long time, and the second user would like toget some results sooner rather than later. The following blocksillustrate one implementation of how security might be checked for afirst user that has a lot of feed items, but the second user cannot seemost of them. This implementation can be used for all situations, butcan be effective in the above situation.

In block 1231, a predetermined number of entries are retrieved from theevent history table (e.g., starting from the most recent, which may bedetermined from the event identifier). The retrieved entries may just beones that match the user ID of the query. In one implementation, entriesare checked to find the entries that are associated with the user andwith a record (i.e. not just posts to the user account). In anotherimplementation, those entries associated with the user are allowed to beviewed, e.g., because the second user can see the profile of the firstuser as determined in block 1220.

In block 1232, the record identifiers are organized by type and the typeis checked on whether the second user can see the record types. Otherchecks such as whether a record was manually shared (e.g., by the owner)can also be performed. In one implementation, the queries for thedifferent types can be done in parallel.

In block 1233, if a user can see the record type, then a check can beperformed on the specific record. In one implementation, if a user cansee a record type, then the user can see all of the records of thattype, and so this block can be skipped. In another implementation, thesharing model can account for whether a user below the second user(e.g., the second user is a manager) can see the record. In such animplementation, the second user may see such a record. In oneimplementation, if a user cannot see a specific record, then comments onthat record are also not viewable.

In block 1234, field level sharing rules can be used to determinewhether the second user can see information about an update or value ofcertain fields. In one implementation, messages can be analyzed todetermine if reference to a particular field name is made. If so, thenfield level security can be applied to the messages.

In block 1280, blocks 1231-1234 are repeated until a stopping criterionis met. In one implementation, the stopping criteria may be when amaximum number (e.g., 100) of entries that are viewable have beenidentified. In another implementation, the stopping criteria can be thata maximum number (e.g., 500) of entries from the entity feed trackedupdate table have been analyzed, regardless of whether the entries areviewable or not.

In one implementation, a news feed can be generated as a combination ofthe profile feeds and the entity feeds, e.g., as described above. In oneimplementation, a list of records and user profiles for the queries inblocks 1110 and 1210 can be obtained form user subscription table 940.In one implementation, there is a maximum number of objects that can befollowed.

E. Partial Pre-Computing of Items for a Feed

FIG. 13 shows a flowchart of an example of a method 1300 of storingevent information for efficient generation of feed items to display in afeed, performed in accordance with some implementations. In variousimplementations, method 1300 can be performed each time an event iswritten to the event history table, or periodically based on some othercriteria (e.g., every minute, after five updates have been made, etc.).

In block 1310, data indicative of an event is received. The data may bethe same and identified in the same way as described for block 1010. Theevent may be written to an event history table (e.g., table 910).

In block 1320, the object(s) associated with the event are identified.In various implementations, the object may be identified by according tovarious criteria, such as the record being changed, the user changingthe record, a user posting a message, and a user whose profile themessage is being posted to.

In block 1330, the users following the event are determined. In oneimplementation, one or more objects that are associated with the eventare used to determine the users following the event. In oneimplementation, a subscription table (e.g., table 940) can be used tofind the identified objects. The entries of the identified objects cancontain an identifier (e.g., user ID 941) of each the users followingthe object

In block 1340, the event and the source of the event, e.g., a record(for a record update) or a posting user (for a user-generated post) arewritten to a news feed table along with an event identifier. In oneimplementation, such information is added as a separate entry into thenews feed table along with the event ID. In another implementation, eachof the events for a user is added as a new column for the row of theuser. In yet another implementation, more columns (e.g., columns fromthe other tables) can be added.

News feed table 960 shows an example of such a table with user ID 961and event ID or pointer 962. The table can be organized in any manner.One difference from event history table 910 is that one event can havemultiple entries (one for each subscriber) in the news feed table 960.In one implementation, all of the entries for a same user are groupedtogether, e.g., as shown. The user U819 is shown as following events E37and E90, and thus any of the individual feed items resulting from thoseevents. In another implementation, any new entries are added at the endof the table. Thus, all of the followers for a new event can be added asa group. In such an implementation, the event IDs would generally begrouped together in the table. Of course, the table can be sorted in anysuitable manner.

In an implementation, if the number of users is small, then the feeditems in one or more of the tables may be written as part of the samewrite transaction. In one implementation, the determination of smalldepends on the number of updates performed for the event (e.g., amaximum number of update operations may be allowed), and if moreoperations are performed, then the addition of the feed items isperformed. In one aspect, the number of operations can be counted by thenumber of rows to be updated, including the rows of the record (whichdepends on the update event), and the rows of the feed tracked updatetables, which can depend on the number of followers. In anotherimplementation, if the number of users is large, the rest of the feeditems can be created by batch. In one implementation, the feed items arewritten as part of a different transaction, i.e., by batch job.

In one implementation, security checks can be performed before an entryis added to the news feed table 960. In this manner, security checks canbe performed during batch jobs and may not have to be performed at thetime of requesting a news feed. In one implementation, the event can beanalyzed and if access is not allowed to a feed item of the event, thenan entry is not added. In one aspect, multiple feed items for a sameuser may not result from a same event (e.g., by how an event is definedin table 910), and thus there is no concern about a user missing a feeditem that he/she should be able to view.

In block 1350, a request for a news feed is received from a user. In oneimplementation, the request is obtained when a user navigates to theuser's home page. In another implementation, the user selects a table,link, or other page item that causes the request to be sent.

In block 1360, the news feed table and other tables are accessed toprovide displayable feed items of the news feed. The news feed can thenbe displayed. In one implementation, the news feed table can then bejoined with the event history table to determine the feed items. Forexample, the news feed table 960 can be searched for entries with aparticular user ID. These entries can be used to identify event entriesin event history table 910, and the proper information from any childtables can be retrieved. The feed items (e.g., feed tracked updates andmessages) can then be generated for display.

In one implementation, the most recent feed items (e.g., 100 mostrecent) are determined first. The other feed items may then bedetermined in a batch process. Thus, the feed item that a user is mostlikely to view can come up first, and the user may not recognize thatthe other feed items are being done in batch. In one implementation, themost recent feed items can be gauged by the event identifiers. Inanother implementation, the feed items with a highest importance levelcan be displayed first. The highest importance being determined by oneor more criteria, such as, who posted the feed item, how recently, howrelated to other feed items, etc.

In one implementation where the user subscription table 940 is used todynamically create a news feed, the query would search the subscriptiontable, and then use the object IDs to search the event history table(one search for each object the user is following). Thus, the query forthe news feed can be proportional to the number of objects that one wassubscribing to. The news feed table allows the intermediate block ofdetermining the object IDs to be done at an earlier stage so that therelevant events are already known. Thus, the determination of the feedis no longer proportional to the number of object being followed.

In some implementations, a news feed table can include a pointer (asopposed to an event identifier) to the event history table for eachevent that is being followed by the user. In this manner, the evententries can immediately be retrieved without having to perform a searchon the event history table. Security checks can be made at this time,and the text for the feed tracked updates can be generated.

X. Display of a Feed

Feeds include messages and feed tracked updates and can show up in manyplaces in an application interface with the database system. In oneimplementation, feeds can be scoped to the context of the page on whichthey are being displayed. For example, how a feed tracked update ispresented can vary depending on which page it is being displayed (e.g.,in news feeds, on a detail page of a record, and even based on how theuser ended up at a particular page). In another implementation, only afinite number of feed items are displayed (e.g., 50). In oneimplementation, there can be a limit specifically on the number of feedtracked updates or messages displayed. Alternatively, the limit can beapplied to particular types of feed tracked updates or messages. Forexample, only the most recent changes (e.g., 5 most recent) for a fieldmay be displayed. Also, the number of fields for which changes aredisplayed can also be limited. Such limits can also be placed on profilefeeds and news feeds. In one implementation, feed items may also besubject to certain filtering criteria before being displayed, e.g., asdescribed below.

XI. Filtering and Searching Feeds

It can be possible that a user subscribes to many users and records,which can cause a user's news feed to be very long and include many feeditems. In such instances, it can be difficult for the user to read everyfeed item, and thus some important or interesting feed items may not beread. In some implementations, filters may be used to determine whichfeed items are added to a feed or displayed in the feed.

FIG. 14 shows a flowchart of an example of a method 1400 for creating acustom feed for users of a database system using filtering criteria,performed in accordance with some implementations. Any of the followingblocks can be performed wholly or partially with the database system,and in particular by one or more processor of the database system.

In block 1410, one or more criteria specifying which feed items are tobe displayed to a first user are received from a tenant. In oneimplementation, the criteria specify which items to add to the customfeed. For example, the criteria could specify to only include feed itemsfor certain fields of a record, messages including certain keywords, andother criteria mentioned herein. In another implementation, the criteriaspecify which items to remove from the custom feed. For example, thecriteria could specify not to include feed items about certain fields orincluding certain keywords.

In block 1420, the database system identifies feed items of one or moreselected objects that match the criteria. The feed items can be storedin the database, e.g., in one or more of the tables of FIG. 9A. In oneimplementation, the one or more selected objects are the objects thatthe first user is following. In another implementation, the one or moreselected objects is a single record whose record feed the first user isrequesting.

In block 1430, the feed items that match the criteria are displayed tothe first user in the custom feed. The generation of text for a feedtracked update can occur after the identification of the feed items(e.g., data for a field change) and before the display of the finalversion of the feed item.

In one implementation, the criteria are received before a feed item iscreated. In another implementation, the criteria are received from thefirst user. In one aspect, the criteria may only used for determiningfeeds to display to the first user. In yet another implementation, thecriteria are received from a first tenant and apply to all of the usersof the first tenant. Also, in an implementation where a plurality ofcriteria are specified, the criteria may be satisfied for a feed item ifone criterion is satisfied.

Some implementations can provide mechanisms to search for feed items ofinterest. For example, the feed items can be searched by keyword, e.g.,as entered by a user. As another example, a tab (or other selectiondevice) can show feed items about or from a particular user. In oneimplementation, only messages (or even just comments) from a particularuser can be selected. Besides searching for feed items that matchcriteria, one also could search for a particular feed item.

XII. Persistent Feeder Component to Display Feed Items

FIG. 15 shows a flowchart of an example of a computer implemented method1500 for providing a persistent feeder component in a user interface todisplay in near real-time feed items when received in information feedsof online social networks, performed in accordance with someimplementations. FIG. 15 is described with reference to the examples ofFIGS. 21-24.

In FIG. 15, at block 1504, a request is received from a computing deviceassociated with a user of a first online social network, such as a usersystem 12 as described above. The request is for feed items of one ormore information feeds. These feeds can include a first information feedassociated with the first online social network, such as Facebook®, asecond information feed associated with a second online social network,such as Chatter® or Twitter®, and additional feeds associated with otheronline social networks.

Examples of online social networks include Chatter®, Yammer®, Facebook®,Twitter®, WordPress®, Blogger®, Tumblr®, Google Plus®, and the like. Auser may have user accounts on the respective online social networks.The user may be browsing among web pages on any one or more of theonline social networks when the request is sent from the user'scomputing device and received at another computing device such as aserver.

In another implementation, at block 1504, the request may be sent andreceived without the user actively interacting with a user interface ofthe online social network. The request may be sent automatically by theuser's computing device at designated time intervals, or after adesignated time period has elapsed. In yet another implementation, therequest may be sent in response to user input indicating the user'sdesire to request an update of feed items in a feeder component.

In some implementations, the request received from the computing devicemay be generated using JavaScript, Asynchronous JavaScript and XML(AJAX), or other client-side technologies. One of ordinary skill in theart will appreciate that other technologies may be used as well,including HTML5.

In FIG. 15, at block 1512, a server or servers performing method 1500 isconfigured to identify one or more of the feed items that satisfy one ormore parameters. A feed item is deemed to satisfy a parameter when thefeed item has one or more attributes satisfying the parameter. Thus theserver can be configured to compare various attributes of the feed itemto the one or more parameters. The one or more parameters are alsosometimes referred to as “criteria”, in some implementations. By way ofexample, at block 1512, the one or more parameters can be stored on andretrieved from any of a variety of storage mediums as disclosed herein.For instance, tenant data storage 22 and/or system data storage 24 ofFIGS. 1A and 1B can store the parameter or parameters. Any of thevarious databases and/or memory devices described herein can serve asstorage media to store and maintain parameter data for retrieval atblock 1512.

A parameter can be generated or selected by a user, as described in theexamples below. Alternatively, such parameters can be system-generatedor selected using any of the various available social network datastored and maintained in the social networking system or systems inwhich method 1500 is practiced. In some implementations, when aparameter is used in conjunction with the identity of a user, theparameter can be stored in association with the user's profile on agiven online social network. For instance, a database table can storeone or more parameters in rows with a column identifying a particularuser's profile with which the parameter or parameters are linked. By thesame token, such parameters can be stored and identified in associationwith records and other constructs of a social networking system.

As described in greater detail below, parameters can identify variouscharacteristics of information updates and other social network data tofilter the data for selective display in one or more feeds. For example,a parameter can identify a keyword, a user who authored a post orcomment, and/or a conversation thread indicated by a sequence ofcomments submitted in direct or indirect response to a previous post orcomment. A number of other examples of parameters and combinations ofparameters can be selected and customized according to the particularimplementation as illustrated in the various examples described below.

In some implementations, the parameters may identify one or more of: auser, a number of users, a role, a title, a group, a record, a field ofa record, a record update, a feed, a conversation thread, a feed item, athreshold number of feed items, and a message. In other implementations,the parameters may also identify one or more of: a keyword, a topic, aphrase, a symbol, an expression, a language, a threshold number ofcharacters, a threshold number of words, a tag, a document, an imagefile, a video file, an audio file, a type of document, a type of file, atime stamp, and a timeframe.

In some implementations, one or more parameters may be determined byuser input data, where the user may specify the one or more parametersin a field of the user's profile on one of the online social networks.In other implementations, one or more parameters may be determined bydefault data of the first online social network. The default data may beselected according to the user privileges level of the first user. Inyet another implementation, one or more parameters may be determined byan administrator of the first online social network.

Returning to block 1512, the server is configured to identify one ormore feed items as having one or more attributes satisfying one or moreparameters. In one implementation, in the context of a group feed,parameters can identify the particular group and a designatedconversation topic, so a subset of the feed items stored and publishedas part of the group feed, for instance, on the topic of client XYZ, canbe identified at block 1512. Parameters can be applied to various dataassociated with the feed items, including the content of an informationupdate as well as header data, attached files, and other data linkedwith or referenced by the information update. For instance, when aparameter identifies a specific user, the author or sender of aparticular feed item will be an attribute at block 1512.

In FIG. 15, at block 1520, the server is configured to transmit theidentified feed items to the user's computing device to be displayed inthe feeder component in the user interface. The feeder component maypersist in the user interface when the user navigates between differentweb pages of the online social network. For example, for a Chatter® userthat is navigating the various pages of the Chatter® user interface, theuser interface may continue to display a persistent feeder componentthat continues to display identified feed items as the user navigatesthe pages of Chatter®. This may allow the user to have continuous accessto his information feed as he works on other Chatter® web pages. Thefeeder component may appear in the form of a textbox superimposed overthe bottom right hand corner, or any other area, of the user interface,allowing the user to view both the feeder component and some of thecontents of the current web page.

In some implementations, the feeder component may be configured todisplay no more than a designated number of feed items, or may beconfigured to automatically remove a feed item after the feed item isdisplayed in the feeder component for more than a designated time. Thismay allow the user to not have to scroll through an unmanageable numberof feed items in the feeder component by removing older feed items fromthe feeder component. In some implementations, the feed items may haverespective timestamps and the feeder component may display theidentified feed items in order of the respective timestamp, providingthe user with a chronological view of the information feeds.

Further, as depicted in FIG. 24, the feeder component may also beconfigured to display next to each identified feed item 2402 a graphicalindicator 2422 representing the information feed that the identifiedfeed item 2402 belongs to. For example, if the first information feed isa Facebook® feed, and the second information feed is a Twitter® feed,then the feeder component may display a Twitter® icon next to theTwitter® feed items, and a Facebook® feed icon 2422 next to theFacebook® feed items 2402. The user may also specify in the userpreferences what icon to associate with each feed. This may allow theuser to quickly distinguish the information feeds associated with thefeed items in the feeder component.

The feeder component may also be displayed in various display formats:as an in-page textbox, a minimized indicator, and a pop-out window.Providing the feeder component in multiple display formats may allow theuser to move and resize the feeder component to more conveniently viewthe contents of the feeder component or the contents of the webpage. Thefeeder component may display icons that the user may click on to changethe display format of the feeder component. In the in-page textboxformat, the feeder component may appear to be part of the current webpage, superimposed over the contents of the webpage.

FIG. 21 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent superimposed over a portion of the page as displayed on adisplay device, according to some implementations. FIG. 21 illustratesan example where a feeder component 2100 is displayed in an in-pagetextbox display format. In this implementation, the feeder component2100 is part of a user interface 2102 and appears superimposed overother items in the user interface 2102. The feeder component 2100 maypersist in the user interface 2102 as the user navigates among the webpages of a first online social network, which is Chatter® in the exampleof FIG. 21. While in the in-page textbox display format, the user may bepresented with a minimize icon 2104 that the user may click to changethe display format of the feeder component 2100 to a minimized indicatordisplay format. The user may also be presented with a pop-out icon 2108that the user may click to change the display format of the feedercomponent 2100 to a pop-out window display format. Further, the user mayalso be presented with a disable icon 2112 that the user may click on todisable the feeder component 2100.

FIG. 22 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent superimposed over a portion of the page as displayed on adisplay device, according to some implementations. FIG. 22 illustratesan example where a feeder component 2200 is displayed in a minimizedindicator display format. In this implementation, the feeder component2200 is part of the user interface 2202 and appears superimposed overother items in the user interface 2202 as an indicator that may besmaller in size than the in-page textbox feeder component 2100 in FIG.21. The feeder component 2200 may persist as a minimized indicator inthe user interface 2202 as the user navigates among the web pages of thefirst online social network, which is Chatter® in the example of FIG.22. While in the minimized indicator display format, the user may bepresented with a maximize icon 2206 that the user may click to changethe display format of the feeder component 2200 to an in-page textbox.The user may also be presented with a pop-out icon 2208 that the usermay click to change the display format of the feeder component 2200 to apop-out window. Further, the user may also be presented with a disableicon 2212 that the user may click on to disable the feeder component2200. While in the minimized indicator display format, the feedercomponent 2200 may not display any feed items. Receiving an updated feeditem at the user's computing device may cause the minimized indicator tochange color. This may indicate to the user that a new feed item isavailable to be displayed in the feeder component.

FIG. 23 shows an example of a graphical user interface (GUI) including apresentation of a social networking page with a feed and a feedercomponent as a separate pop-out window superimposed over a portion ofthe page as displayed on a display device, according to someimplementations. FIG. 23 illustrates an example where the feedercomponent 2300 is displayed in a pop-out window display format. In thisimplementation, the feeder component 2300 is displayed in a separatewindow 2301, distinct from the user interface 2302 in which the user isbrowsing the web pages of the first social network. While the userbrowses the web pages of the first social network in the user interface2302, the feeder component may persist in the separate window 2301.While in the pop-out window display format, the user may be presentedwith a pop-in icon 2310 that the user may click to change the displayformat of the feeder component 2300 to an in-page textbox. The user mayalso be presented with a disable icon 2312 that the user may click todisable the feeder component 2300. In some implementations, disablingthe feeder component 2300 may also cause the separate window 2301 inwhich the feeder component 2300 is displayed to close.

In some implementations, when the feeder component is in a disabledstate, the user may change the state of the feeder component to theenabled state by selecting an option in a user dropdown menu at the topof the user interface.

FIG. 24 shows a zoomed-in view of an example of a graphical userinterface (GUI) including a presentation of a social networking pagewith a feed and a feeder component superimposed over a portion of thepage as displayed on a display device, according to someimplementations. FIG. 24 illustrates a feeder component 2400 in thein-page textbox display format. The features of the feeder component2400 described in this paragraph may also be presented in the otherdisplay formats described above, for instance, with reference to FIGS.21-23. A feed item 2402 displayed in the feeder component 2400 maycontain social networking data indicating items such as: a sender 2404of the feed item 2402, a sender avatar 2406, a recipient 2408, arecipient avatar 2436, contents 2410 of the feed item 2402, a timestamp2412 of the feed item 2402, a comment link 2414 for the user to commenton the feed item 2402, a comment textbox 2416 for the user to comment onthe feed item 2402, a like link 2418 for the user to “like” the feeditem 2402, a delete link 2420 for the user to remove the feed item 2402from the feeder component 2400, and a feed icon 2422 to indicate thesource feed of the feed item 2402. In some implementations, the sourcefeed may be the information feed from which the feed item 2402 orinformation update is received. For example, if the feed item 2402 is atweet from a Twitter® feed, the feed icon 2422 may be a Twitter® icondisplayed by the feed item 2402. The feed icon 2422 may allow a user tomore quickly scan through the feeder component 2400 and see which feeditems 2402 belong to which information feed. The feeder component 2400may also contain a status textbox 2424 for the user to update his statusfor a source feed. Moreover, the status textbox 2424 may contain asecond feed icon 2426 to indicate the source feed to which the statuswill be posted. The feeder component 2400 may contain display formaticons 2430, 2432 that the user may click to change the display format ofthe feeder component 2400. The feeder component 2400 may also contain adisable link 2434 to disable the feeder component. The feeder component2400 may also contain a refresh link 2428 that the user may click torefresh the feeder component by sending a request for updated feed itemsto the server configured to perform methods 1500, 1600, and 1700. Inother implementations, the feeder component may also contain a fileupload box or a list of online users of the first online social network.

As illustrated in FIG. 24, a user may not only read information updatesin the feeder component, but may also respond to individual informationupdates in the feeder component, rather than having to load the actualfeed in another webpage in the user interface. This could allow a userto conveniently receive and respond to feed information without havingto navigate away from a web page that the user is viewing or working onat the moment. For instance, a user may be reading through informationon a case loaded in the user interface in Chatter®, when he receives aFacebook® message. The feeder component allows the user to be notifiedof the Facebook® message without requiring the user to have Facebook®open in a separate window. Moreover, the user may comment on the messagedirectly by typing his comment in the comment textbox 2416 of the feedercomponent without having to navigate away from the case information inChatter® that he is currently working on. As another example, the usermay, upon receiving a Facebook® message, wish to update his Facebook®status to indicate that he is currently busy. He may do so by enteringand submitting his status through the status textbox 2424 of the feedercomponent 2400, without having to navigate to a Facebook® user interfaceto update his status.

Returning to FIG. 15, at block 1520, the feeder component is configuredto persist in the user interface when the user interface changes fromdisplaying one web page to displaying another web page. For example, theChatter® user interface may continuously display the feeder componentover the Chatter® web page as various Chatter® web pages are displayedto the user. In some implementations, the web pages being displayed maybe of an online social network different from the online social networksof the feed items being displayed in the feeder component. As anexample, a Chatter® user may configure his Chatter® feeder component todisplay information updates from a Twitter® feed and a Facebook® feed.Providing a persistent feeder component may allow a user to keep trackof Twitter® and Facebook® information updates that the user isinterested in while navigating the various web pages of Chatter®.

FIG. 16 shows a flowchart of an example of a computer implemented method1600 for providing a persistent feeder component in a user interface todisplay in near real-time feed items when received in information feedsof online social networks, performed in accordance with someimplementations. FIG. 16 is described with reference to the examples ofFIGS. 21-24.

In FIG. 16, at block 1604, a server performing method 1600 receives arequest from a computing device associated with a user of a first onlinesocial network, such as a user system 12 as described above. The requestis for feed items of one or more information feeds. As discussed aboveat block 1504, these feeds can include a first information feedassociated with the first online social network, such as Facebook®, asecond information feed associated with a second online social network,such as Chatter® or Twitter®, and additional feeds associated with otheronline social networks. The first user has first login credentials andsecond login credentials, the first login credentials providing accessto the first online social network, the second login credentialsproviding access to the second online social network. In someimplementations, the first and second login credentials may be usernames and passwords for access to the respective online social networks.For example, a user may be required to enter his Twitter® user name andpassword to access his Twitter® updates, as well as his Chatter® username and password to access his Chatter® information updates. In someimplementations, other types of login credentials, such as a token, asecret key, or a public-private key pair, may be used as well.

In some implementations, the login credentials may provide limitedaccess to the user's information feed and personal data on the onlinesocial network. For instance, the login credentials may provide thecomputing device with access to a subset of the user's information onthe online social network. The limited access provided to the computingdevice may also prevent the computing device from changing the user'ssettings on the online social network. For example, the second logincredentials for the second online social network may provide read-onlyaccess to a specific information feed of the user's account on thesecond online social network, providing more robust security for theuser's accounts on the first and second online social networks.

In FIG. 16, at block 1606, the server retrieves feed items from thefirst information feed using the first login credentials. In oneimplementation, the first login credentials give the server access toinformation updates from the first information feed of the first onlinesocial network. The server may send the first login credentials to aserver of the first online social network, after which the server of thefirst online social network authenticates the computing device and givesthe computing device access to the resources of the user's account onthe first online social network. The now-authenticated computing devicemay now retrieve feed items of the first information feed from theserver of the first online social network.

In FIG. 16, at block 1608, the server retrieves feed items from thesecond information feed using the second login credentials. In oneimplementation, the user may submit the second login credentials to theserver, and the server may submit the second login credentials to thesecond online social network for authentication and access to the feeditems of the second online social network.

In another implementation, the user may submit his user name andpassword directly to the second online social network, and the secondonline social network may return an access token either to the user,wherein the user shares the access token with the first online socialnetwork for access to feed items in the second online social network, orthe second online social network may send the access token directly tothe first online social network. This arrangement has the advantage ofproviding the first online social network access to the user's feeditems in the second online social network without requiring the user toshare his user name and password with the first online social network.In some implementations, the access token may provide limited access todata on the second online social network, allowing a user to limit whatthe server of the first online social network can access on the secondonline social network. In some implementations, the authenticationprocess may be carried out with protocols such as OpenID or OAuth.

In FIG. 16, at block 1612, the server identifies one or more of the feeditems as satisfying one or more parameters, where the identified feeditems have one or more attributes satisfying the one or more parameters,as generally described above at block 1512 of method 1500.

In FIG. 16, at block 1620, the server transmits the identified feeditems to the user's computing device to be displayed in the feedercomponent of the user interface. The feeder component may persist in theuser interface when the user navigates between the different web pagesof the online social network, as generally described above at block 1520of method 1500.

FIG. 17 shows a flowchart of an example of a method 1700 for providing apersistent feeder component in a user interface to display in nearreal-time feed items when received in information feeds of online socialnetworks, performed in accordance with some implementations. FIGS. 17-20are described with reference to the examples of FIGS. 21-24.

In FIG. 17, at block 1704, a server performing method 1700 receives arequest from a computing device associated with a user of a first onlinesocial network, such as a user system 12 as described above. The requestis for feed items of one or more information feeds. These feeds includea first information feed associated with the first online social networkand a second information feed associated with a second online socialnetwork, and the user has first and second login credentials providingaccess to the first and second online social networks, as generallydescribed above at block 1604 of method 1600.

In FIG. 17, at block 1706, the server retrieves feed items from thefirst information feed, as generally described above at block 1506 ofmethod 1500. In FIG. 17, at block 1708, the server retrieves feed itemsfrom the second information feed using the second login credentials, asgenerally described above at block 1608 of method 1600. In FIG. 17, atblock 1712, the server identifies one or more of the feed items ashaving one or more attributes satisfying one or more parameters, asgenerally described above at block 1512 of method 1500.

In FIG. 17, at block 1720, the server transmits the identified feeditems to the user's computing device to be displayed in the feedercomponent of the user interface. The feeder component may persist in theuser interface when the user navigates between the different web pagesof the online social network, as generally described above at block 1520of method 1500.

In some implementations, a user interested in tracking activity on anonline social network may specify one or more milestones of activitythat the user would like to be notified of when the activity on thesecond online social network meets at least one of the one or moremilestones. The user may specify the milestones in the user's profile inthe first online social network. In one implementation, the user mayprovide in his first online social network user profile hisauthentication credentials for the second online social network toprovide access to the second online social network to obtain activityinformation on the second online social network. As an example of amilestone, a Chatter® user navigating the Chatter® website may beinterested in receiving a notification in his Chatter® feeder componentwhen the number of Twitter® followers of his Twitter® user accountexceeds a designated number. In this example, the Chatter® user mayprovide his Twitter® authentication information in his Chatter® userprofile so that the Chatter® application may obtain access to the user'sTwitter® activity information. Alternatively, the Chatter® user maydirectly provide his Twitter® authentication information to the Twitter®application and receive an access token that the Chatter® applicationmay use to access the user's Twitter® activity information. Otherexamples of milestones include receiving a notification when the numberof retweets of a designated tweet exceeds a designated number, or whenthe number of tweets including a designated hashtag exceeds a designatednumber, or when the number of Facebook® likes of a designated web pageexceeds a designated number. In another implementation, the user mayalso specify a message associated with a milestone to be displayed tothe user when the milestone is met by activity on the second onlinesocial network.

In FIG. 17, at block 1722, the server determines whether one or moremilestones have been met by activity on the second online socialnetwork. As discussed above, the user may set the milestones that hewishes to be notified about. The determination of whether a milestonehas been met may be made by the server by using an API of the secondonline social network. In some implementations, an API of the secondonline social network may be used to obtain activity information fromthe second online social network.

In other implementations, another user—such as an administrator, asupervisor of the first user, or a second user—may determine themilestones that the first user will be notified about. For example, asupervisor may wish for a group of users to be notified when aparticular milestone that the supervisor sets is achieved. In such anexample, the each user of the group of users may be notified that themilestone is achieved, and they may be prompted to perform specificactions upon achievement of the milestone, where the specific actionsare also designated by the supervisor.

Examples of the activity information that an API may provide include: anumber of tweets including a designated hashtag, a number of Facebook®likes of a designated Facebook® page, a number of retweets of adesignated tweet, etc. As another example, the Twitter® API allows anauthenticating user to obtain, among other things, a list of usersfollowing the authenticating user, a list of users that theauthenticating user is following, a list of tweets that theauthenticating user has authored, and a list of tweets matching aspecified query. The Twitter® API does this by providing a set of classdefinitions (tweets, users, entities, places, etc.) and a set ofbehaviors or methods associated with those classes. The API thusprovides the methods by which a non-Twitter® server may interact withthe objects derived from the Twitter® class definitions. As an example,the API may provide a method that can be called with a tweet, and themethod may return the number of times that the tweet has been retweeted.In this way, the Twitter® API allows a non-Twitter® server to havelimited access to information stored on the Twitter® servers throughspecified methods that return various types of information.

Returning to block 1722, once the computing device obtains the activityinformation from the second online social network, it may compare thatactivity information with the one or more milestones designated by theuser to determine whether any of the milestones have been met.

FIG. 2C illustrates an implementation wherein two on-demand databaseservice environments operate as a first online social network 200A and asecond online social network 200B, wherein a server 280A of the firstonline social network 200A is configured to perform method 1700. Whenserver 280A performs block 1722 of FIG. 17, server 280A sends an APIrequest to the API 260 of the second online social network 200B,requesting information about activity on the second online socialnetwork. The API request may contain authentication information topermit the server 280A to obtain access to the activity information, andthe ACS server 280B of the second online social network may verify theauthentication information and allow access to the activity information.

In some implementations, block 1722 may be executed periodically. Forexample, a server performing method 1700 may execute an API call to thesecond online social network at regular intervals of time to obtainactivity information from the second online social network. The regularinterval of time may be every five seconds, every minute, every hour,etc. Once the server receives the activity information, the server maythen determine whether one or more of the milestones has been met.

In FIG. 17, at block 1724, when one of the milestones has been met byactivity on the second online social network, the server transmits datato the computing device to display a notification in the feedercomponent. In some implementations, the notification displayed in thefeeder component indicates to the user that one of the one or moremilestones that he designated in his user profile of the first onlinesocial network has been met. The notification may also contain morespecific information about the activity that has met the milestone. Forexample, if the milestone was exceeding a target number of tweetsincluding a designated hashtag, the notification displayed in the feedercomponent may include the designated hashtag, the target number oftweets, and the actual number of tweets including the designatedhashtag. In other implementations, the feeder component may also changecolors to draw attention to the notification.

In yet another implementation, the notification may display a message ora call to action to the user to perform a particular action in responseto the notification. For example, a user may be interested in trackingTwitter® activity to see how popular a particular subject or hashtag,say #EURO2012, is among Twitter® users, and the user may wish to launcha marketing campaign related to “EURO 2012” once the volume of activitypertaining to “EURO 2012” reaches a certain level. In such a case, oncethe milestone is reached, the notification displayed to the user mayinclude: “EURO2012 milestone has been met. Launch EURO 2012 marketingcampaign.” This way, a Chatter® user who is interested in launching amarketing campaign once interest in a subject on Facebook® or Twitter®or any other second online social network reaches a certain volume canset his Chatter® user profile parameters to notify him via the Chatter®feeder component when Facebook® or Twitter® activity has reached thatvolume and prompt the user what to do when that milestone is reached.

In FIG. 17, at block 1730, the server is configured to receive andrespond to various types of user input data. Block 1730 can beimplemented as various methods described below with reference to FIGS.18-20.

FIG. 18 shows a flowchart of an example of a method 1830 for receivingand responding to user input data, as one of various implementations ofblock 1730 of method 1700. In FIG. 18, at block 1832, a server providesan instruction to the computing device to display in the feedercomponent a prompt for user input data in response to an identified feeditem.

FIG. 24 illustrates a feeder component 2400 that contains variousprompts for user input to allow a user to respond to a feed item 2402 inthe feeder component 2400 without having to navigate to a web page ofthe information feed of the online social network associated with thefeed item 2402. As one example, a user may click on the comment link2414 to respond to the feed item 2402 with a comment. Clicking on thecomment link 2414 may cause a comment textbox 2416 to appear in thefeeder component 2400, in which a user may type the contents of hiscomment to be sent to the online social network associated with the feeditem 2402. As another example, the computing device may display a likelink 2418 in the feeder component 2400 that a user may click on to“like” the feed item 2402. In another example, the computing device maydisplay a refresh link 2428 that a user may click on to refresh andupdate the feed items in the feeder component 2400. In yet anotherexample, the computing device may display a status textbox 2424 in thefeeder component 2400, in which a user may update his status in theonline social network associated with the status textbox 2424 by typingthe contents of his updated status in the status textbox 2424.

In some implementations, the prompt may allow a user to indicate that hewishes for more feed items and information updates with attributes thatare similar to the attributes of the feed item that the prompt isassociated with to be displayed in the feeder component. For example,the feed item may include a prompt, such a “like” link, a thumbs upicon, a “more like this” link, or the like, which the user may click onto provide a positive indication of personal preference. The server maythen add one or more of the attributes of the feed item to the one ormore parameters used by the server at blocks 1512, 1612, and 1712 foridentifying future feed items to display in the feeder component. Thismay allow the user to continue to tailor his preferences as to what feeditems to display in the feeder component by responding to feed itemsthat are displayed in the feeder component.

Similarly, the user may also indicate a negative indication of personalpreference by clicking on a prompt associated with a feed item. Theprompt may be a “dislike” link or a thumbs down icon or the like. Whenthe user does this, the server may respond by removing one or more ofthe attributes of the feed item from the one or more parameters used bythe server at blocks 1512, 1612, and 1712 for identifying future feeditems to be displayed in the feeder component.

In other implementations, the prompt may allow a user to indicate thathe wishes for the feed item to be removed from the feeder component. Forexample, the feed item may include a prompt like “remove” or “delete”that the user may click on to instruct the server to remove the feeditem from the display of the feeder component.

In FIG. 18, at block 1834, a server performing method 1830 receives fromthe computing device the user response. In some implementations, asillustrated in FIG. 24, when the user clicks on the like link 2418 orthe comment link 2414 and enters a comment in the comment textbox 2416,the computing device will transmit the user response back to the serverand the server will receive the user response from the computing device.

In FIG. 18, at block 1836, the server transmits the user response to theonline social network associated with the identified feed item. In someimplementations, the server may transmit the user response to the onlinesocial network associated with the identified feed item using an API andlogin credentials for the online social network. In anotherimplementation, the server may have an access token that it may use withan API to transmit the user response to the online social network,obviating the need of the user to provide to a first online socialnetwork login credentials to a second online social network. Thispermits a user to post content to his user account on a second onlinesocial network from a feeder component in the user interface of a firstonline social network.

As illustrated in FIG. 24, the user may type “posting comment” in thecomment textbox 2416 to post a comment in response to the Facebook® feeditem 2402 that is displayed in the feeder component 2400. Moreover, theuser may also type “Posting my status from feeder component” in thestatus textbox 2424 to update the status on his Twitter® account. As theuser is entering his status in the status textbox 2424, the source feedicon 2426 lets the user know which information feed's status he isupdating by posting his status from the feeder component.

FIG. 19 shows a flowchart of an example of a method 1930 for receivingand responding to user input data, as another one of variousimplementations of block 1730 of method 1700. In FIG. 19, at block 1932,a server performing method 1930 provides an instruction to the computingdevice to display in the feeder component a prompt for user input data.

FIG. 22 illustrates a feeder component 2200 that contains various linksfor user input to allow a user to change the display format of thefeeder component 2200. The feeder component 2200 in FIG. 22 is displayedin the minimized indicator format. When the feeder component 2200 isdisplayed in this format, the feeder component 2200 may contain amaximize link 2206 and a pop-out link 2208. Clicking on the maximizelink 2206 may cause the display format of the feeder component 2200 tochange to the in-page textbox format. Clicking on the pop-out link 2208may cause the display format of the feeder component 2200 to change tothe pop-out window format.

FIG. 23 illustrates a feeder component 2300 that contains various linksfor user input to allow a user to change the display format of thefeeder component 2300. The feeder component 2300 in FIG. 23 is displayedin the pop-out window format. When the feeder component 2300 isdisplayed in this format, the feeder component 2300 may contain a pop-inlink 2310. Clicking on the pop-in link 2310 may cause the display formatof the feeder component 2300 to change to the in-page textbox format.

FIG. 24 illustrates a feeder component 2400 that contains various linksfor user input to allow a user to change the display format of thefeeder component 2400. The feeder component 2400 in FIG. 24 is displayedin the in-page textbox format. When the feeder component 2400 isdisplayed in this format, the feeder component 2400 may contain aminimize link 2430 and a pop-out link 2432. Clicking on the minimizelink 2430 may cause the display format of the feeder component 2400 tochange to the minimized indicator format. Clicking on the pop-out link2432 may cause the display format of the feeder component 2400 to changeto the pop-out window format.

In FIG. 19, at block 1934, a server performing method 1930 receives aninstruction to change the display format of the feeder component. In oneimplementation, as illustrated in FIG. 24, when the user clicks on theminimize link 2430, the computing device will transmit an instructionback to the server and the server will receive the instruction from thecomputing device to change the display format of the feeder component.

In FIG. 19, at block 1936, a server performing method 1930 changes thedisplay format of the feeder component according to the instruction. Insome implementations, the server may send an instruction to thecomputing device to change the display format of the feeder component.

FIG. 20 shows a flowchart of an example of a method 2030 for receivingand responding to user input data, as yet another one of variousimplementations of block 1730 of method 1700. In FIG. 20, at block 2032,a server performing method 2030 provides an instruction to the computingdevice to display in the feeder component a prompt for user input data.In some implementations, the prompt may be an icon or a text link thatthe user may click on. In FIG. 20, at block 2034, the server receives aninstruction to change the state of the feeder component between theenabled and disabled states. For example, if the current state of thefeeder component is enabled, the prompt displayed in the feedercomponent may cause an instruction to disable the feeder component to besent when the user clicks on the prompt. In FIG. 20, at block 2036, theserver changes the state of the feeder component according to theinstruction, wherein the disabled state causes the feeder component tobe hidden or reduced in size in the user interface. In someimplementations, if the feeder component is not visible when it is in adisabled state, the user may be required to open a user preferences menuto change the feeder component to an enabled state.

FIG. 24 illustrates a feeder component 2400 that contains a disable link2434 that a user may click on to disable the feeder component 2400. Insome implementations, changing the state of the feeder component 2400from an enabled state to a disabled state may cause the feeder component2400 to not be displayed in the user interface. Because the feedercomponent in the enabled state is regularly requesting feed items anddisplaying feed items, disabling the feeder component may reduce networkbandwidth use. In some implementations, a disabled feeder component maybe enabled by changing the user profile settings in the first onlinesocial network. In another implementation, a disabled feeder componentmay still be visible in the user interface, but reduced in size. In sucha case, the disabled feeder component may be enabled in response to theuser clicking a link displayed in the disabled feeder component.

The specific details of the specific aspects of implementationsdisclosed herein may be combined in any suitable manner withoutdeparting from the spirit and scope of the disclosed implementations.However, other implementations may be directed to specificimplementations relating to each individual aspect, or specificcombinations of these individual aspects.

While the disclosed examples are often described herein with referenceto an implementation in which an on-demand database service environmentis implemented in a system having an application server providing afront end for an on-demand database service capable of supportingmultiple tenants, the present implementations are not limited tomulti-tenant databases nor deployment on application servers.Implementations may be practiced using other database architectures,i.e., ORACLE®, DB2® by IBM and the like without departing from the scopeof the implementations claimed.

It should be understood that some of the disclosed implementations canbe embodied in the form of control logic using hardware and/or usingcomputer software in a modular or integrated manner. Other ways and/ormethods are possible using hardware and a combination of hardware andsoftware.

Any of the software components or functions described in thisapplication may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructionsor commands on a computer-readable medium for storage and/ortransmission, suitable media include random access memory (RAM), a readonly memory (ROM), a magnetic medium such as a hard-drive or a floppydisk, or an optical medium such as a compact disk (CD) or DVD (digitalversatile disk), flash memory, and the like. The computer-readablemedium may be any combination of such storage or transmission devices.Computer-readable media encoded with the software/program code may bepackaged with a compatible device or provided separately from otherdevices (e.g., via Internet download). Any such computer-readable mediummay reside on or within a single computing device or an entire computersystem, and may be among other computer-readable media within a systemor network. A computer system, or other computing device, may include amonitor, printer, or other suitable display for providing any of theresults mentioned herein to a user.

While various implementations have been described herein, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of the present applicationshould not be limited by any of the implementations described herein,but should be defined only in accordance with the following andlater-submitted claims and their equivalents.

What is claimed is:
 1. A computer implemented method for providing apersistent feeder component in a user interface to display in nearreal-time feed items when received in feeds of a plurality of socialnetworking systems, the method comprising: receiving, from a computingdevice associated with a first user of a first social networking systema request for feed items of one or more of the feeds, the feedsincluding a first feed associated with the first social networkingsystem having first login credentials and a second feed associated witha second social networking system having second login credentials, thefirst login credentials being independent from the second logincredentials; identifying one or more of the feed items as having one ormore attributes satisfying one or more parameters; causing display of,on a display of the computing device, in the feeder component in theuser interface the identified one or more feed items, the feedercomponent being configured to persist in the user interface when theuser interface changes from a first state in which a first page isdisplayed to a second state in which a second page is displayed, thefeeder component comprising a first publisher configured to publish feeditems to the first feed and the feeder component comprising a secondpublisher configured to publish feed items to the second feed;determining, using an application programming interface (API), thatactivity on the second social networking system has a characteristic,including determining that one or more milestones have been met by theactivity on the second social networking system, the API beingconfigured to provide activity information corresponding to the activityon the second social networking system, the one or more milestones beingspecified by an administrator or a second user of the first socialnetworking system; and causing display of, on the display of thecomputing device and responsive to determining that the activity on thesecond social networking system has the characteristic, both: a visualindicator in association with the feeder component, the visual indicatorindicating that the activity on the second social networking system hasthe characteristic, and a message in association with the feedercomponent, the message comprising a recommendation that the first userperform an action in response to the activity on the second socialnetworking system having the characteristic, the action being a task tocarry out an operation of business of an enterprise, the first userbeing an employee of the enterprise.
 2. The method of claim 1, thefeeder component configured to display no more than a designated numberof feed items.
 3. The method of claim 1, the feeder component configuredto automatically remove feed items after the feed items are displayed inthe feeder component for a designated time.
 4. The method of claim 1,the feeder component configured to display proximate to each identifiedfeed item a graphical indicator identifying the feed of the respectiveidentified feed item.
 5. The method of claim 1, the feed items havingrespective timestamps, the feeder component configured to display theidentified one or more feed items in order of the respective timestamp.6. The method of claim 1, wherein the second login credentials compriseone or more access tokens from the second social networking system,wherein the one or more access tokens are received in response to validauthentication information being provided to the second socialnetworking system.
 7. The method of claim 1, wherein the first pageincludes a first component configured to display the first feed or thesecond feed, and the second page includes a second component configuredto display a feed different from the feed displayed at the firstcomponent.
 8. The method of claim 1, the one or more milestonesincluding one or more of: a number of followers, a number of likes, anumber of shares, a number of comments, a number of views, and a numberof re-tweets.
 9. The method of claim 1, wherein the feed items includeone or more of: a post, a comment, an indication of personal preference,a status update, a user-submitted hyperlink, and an uploaded file. 10.The method of claim 1, wherein the one or more parameters identify oneor more of: a user, a number of users, a role, a title, a group, arecord, a field of a record, a record update, a feed, a conversationthread, a feed item, a threshold number of feed items, and a message.11. The method of claim 1, wherein the one or more parameters identifyone or more of: a keyword, a topic, a phrase, a symbol, an expression, alanguage, a threshold number of characters, a threshold number of words,a tag, a document, an image file, a video file, an audio file, a type ofdocument, a type of file, a time stamp, and a timeframe.
 12. The methodof claim 1, wherein user input data determines the one or moreparameters.
 13. The method of claim 1, wherein the first socialnetworking system defines default data of the one or more parameters.14. The method of claim 13, the first user having a user privilegeslevel, wherein the default data is selected according to the userprivileges level.
 15. The method of claim 1, wherein an administrator ofthe first social networking system determines the one or moreparameters.
 16. The method of claim 1, further comprising: providing aninstruction to the computing device to display in the feeder component aprompt for user input data in response to an identified feed item;receiving from the computing device the user input data; andtransmitting the user input data to the social networking systemassociated with the identified feed item.
 17. The method of claim 16,wherein the user input data includes one or more of: a post, a comment,a like, a dislike, a share, a status update, a user-submitted hyperlink,an image file, a video file, and an audio file.
 18. The method of claim16, the user input data including a positive indication of personalpreference, the method further comprising: adding one or more attributesof the identified feed item to the one or more parameters.
 19. Themethod of claim 16, the user input data including a negative indicationof personal preference, the method further comprising: removing one ormore attributes of the identified feed item from the one or moreparameters.
 20. The method of claim 16, the user input data requestingremoval of the identified feed item from the feeder component, themethod further comprising: removing the identified feed item from thefeeder component.
 21. The method of claim 1, wherein the feedercomponent is displayed in a format being one of: an in-page textbox, aminimized indicator, and a window separate from the pages.
 22. Themethod of claim 1, wherein the feeder component is superimposed over aportion of a displayed page.
 23. The method of claim 1, the feedercomponent configured to change color responsive to the data beingreceived at the computing device.
 24. The method of claim 1, the feedercomponent configured to have a display format, the method furthercomprising: providing an instruction to the computing device to displayin the feeder component a prompt for user input data; receiving aninstruction to change the display format of the feeder component; andchanging the display format of the feeder component according to theinstruction.
 25. The method of claim 1, the feeder component configuredto have an enabled state and a disabled state, the method furthercomprising: receiving an instruction to change the state of the feedercomponent between the enabled and disabled states; and changing thestate of the feeder component according to the instruction.
 26. Themethod of claim 25, wherein the disabled state causes the feedercomponent to be hidden or reduced in size in the user interface.
 27. Asystem for providing a persistent feeder component in a user interfaceto display in near real-time feed items when received in feeds of aplurality of social networking systems, the system comprising: a serversystem of a database system, the server system comprising one or morehardware processors operable to execute one or more instructions tocause: processing a request from a computing device associated with afirst user of a first social networking system for feed items of one ormore of the feeds, the feeds including a first feed associated with thefirst social networking system having first login credentials and asecond feed associated with a second social networking system havingsecond login credentials, the first login credentials being independentfrom the second login credentials; identifying one or more of the feeditems as having one or more attributes satisfying one or moreparameters; displaying, on a display of the computing device, in thefeeder component in the user interface the identified one or more feeditems, the feeder component being configured to persist in the userinterface when the user interface changes from a first state in which afirst page is displayed to a second state in which a second page isdisplayed, the feeder component comprising a first publisher configuredto publish feed items to the first feed and the feeder componentcomprising a second publisher configured to publish feed items to thesecond feed; determining, using an application programming interface(API), that activity on the second social networking system has acharacteristic, including determining that one or more milestones havebeen met by the activity on the second social networking system, the APIbeing configured to provide activity information corresponding to theactivity on the second social networking system, the one or moremilestones being specified by an administrator or a second user of thefirst social networking system; and displaying, on the display of thecomputing device and responsive to determining that the activity on thesecond social networking system has the characteristic, both: a visualindicator in association with the feeder component, the visual indicatorindicating that the activity on the second social networking system hasthe characteristic, and a message in association with the feedercomponent, the message comprising a recommendation that the first userperform an action in response to the activity on the second socialnetworking system having the characteristic, the action being a task tocarry out an operation of business of an enterprise, the first userbeing an employee of the enterprise.
 28. A non-transitorycomputer-readable storage medium storing instructions configured tocause a method to be performed for providing a persistent feedercomponent in a user interface to display in near real-time feed itemswhen received in feeds of a plurality of social networking systems, themethod comprising: processing a request from a computing deviceassociated with a first user of a first social networking system forfeed items of one or more of the feeds, the feeds including a first feedassociated with the first social networking system having first logincredentials and a second feed associated with a second social networkingsystem having second login credentials, the first login credentialsbeing independent from the second login credentials; identifying one ormore of the feed items as having one or more attributes satisfying oneor more parameters; causing display of, on a display of the computingdevice, in the feeder component in the user interface the identified oneor more feed items, the feeder component being configured to persist inthe user interface when the user interface changes from a first state inwhich a first page is displayed to a second state in which a second pageis displayed, the feeder component comprising a first publisherconfigured to publish feed items to the first feed and the feedercomponent comprising a second publisher configured to publish feed itemsto the second feed; determining, using an application programminginterface (API), that activity on the second social networking systemhas a characteristic, including determining that one or more milestoneshave been met by the activity on the second social networking system,the API being configured to provide activity information correspondingto the activity on the second social networking system, the one or moremilestones being specified by an administrator or a second user of thefirst social networking system; and causing display of, on the displayof the computing device and responsive to determining that the activityon the second social networking system has the characteristic, both: avisual indicator in association with the feeder component, the visualindicator indicating that the activity on the second social networkingsystem has the characteristic, and a message in association with thefeeder component, the message comprising a recommendation that the firstuser perform an action in response to the activity on the second socialnetworking system having the characteristic, the action being a task tocarry out an operation of business of an enterprise, the first userbeing an employee of the enterprise.